[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: State of the repository conversion

From: Eli Zaretskii
Subject: Re: State of the repository conversion
Date: Fri, 21 Mar 2014 12:17:02 +0200

> From: Steinar Bang <address@hidden>
> Date: Fri, 21 Mar 2014 10:53:18 +0100
> >>>>> Eli Zaretskii <address@hidden>:
> > Thanks.  However, I cannot easily map this arrangement to what I had
> > in mind, namely, having a separate trunk and release branches, each
> > one having its working tree in a different directory.  What am I
> > missing?
> Ok, so you want separate working directories of the official master and
> release branches?


> I have satisfied this requirement for myself, by simply having separate
> clones, something like this:
>  cd ~/git
>  git clone http://somewhere/emacs.git
>  git clone --branch release-23.4 http://somewhere/emacs.git emacs-release-23.4
>  git clone --branch release-24.0 http://somewhere/emacs.git emacs-release-24.0

Yes, that's the obvious possibility.  I thought there were others.


> > As for feature branches, I think relatively short-lived ones will be
> > better off in the same directory as the trunk, because they aren't
> > expected to diverge too much, so having them co-located actually makes
> > a lot of sense and saves time.
> By "co-located", do you mean one .git directory serving multiple working
> directories?

No, I meant in the same working directory, using "git checkout" to
switch between branches.

> >> Downsides to a git repository backing multiple working directories, are:
> >> - 3 copies of the git repository on disk, rather than just one
> > Doesn't --separate-git-dir solve that problem?
> I don't know.  I have never used this.

Andreas said this is not a solution.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]