From: Eli Zaretskii <eliz@gnu.org>
To: Steinar Bang <sb@dod.no>
Cc: emacs-devel@gnu.org
Subject: Re: State of the repository conversion
Date: Fri, 21 Mar 2014 12:17:02 +0200 [thread overview]
Message-ID: <83mwgj6eld.fsf@gnu.org> (raw)
In-Reply-To: <upzcob0zop2p.fsf@dod.no>
> From: Steinar Bang <sb@dod.no>
> Date: Fri, 21 Mar 2014 10:53:18 +0100
>
> >>>>> Eli Zaretskii <eliz@gnu.org>:
>
> > 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?
Right.
> 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.
Thanks.
> > 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.
next prev parent reply other threads:[~2014-03-21 10:17 UTC|newest]
Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-19 17:51 State of the repository conversion Eric S. Raymond
2014-03-19 18:14 ` Paul Eggert
2014-03-19 18:31 ` Eli Zaretskii
2014-03-19 18:54 ` Eric S. Raymond
2014-03-19 19:17 ` Eli Zaretskii
2014-03-20 0:08 ` Stephen J. Turnbull
2014-03-20 0:32 ` Eric S. Raymond
2014-03-20 1:01 ` Óscar Fuentes
2014-03-20 3:55 ` Eli Zaretskii
2014-03-20 4:09 ` Óscar Fuentes
2014-03-20 7:06 ` David Engster
2014-03-20 7:49 ` Steinar Bang
2014-03-20 16:35 ` Eli Zaretskii
2014-03-20 12:42 ` Óscar Fuentes
2014-03-20 14:03 ` Stefan
2014-03-20 15:09 ` Óscar Fuentes
2014-03-20 16:13 ` Eli Zaretskii
2014-03-20 20:23 ` Steinar Bang
2014-03-20 4:04 ` Eli Zaretskii
2014-03-20 4:25 ` Óscar Fuentes
2014-03-20 4:59 ` Stefan
2014-03-20 7:36 ` Steinar Bang
2014-03-20 7:48 ` Florian Weimer
2014-03-20 8:07 ` Steinar Bang
2014-03-20 16:19 ` Eli Zaretskii
2014-03-20 18:02 ` Stefan
2014-03-20 18:09 ` David Kastrup
2014-03-20 20:35 ` Steinar Bang
2014-03-20 18:15 ` Eli Zaretskii
2014-03-20 18:44 ` Stefan
2014-03-20 20:17 ` Eli Zaretskii
2014-03-20 20:30 ` Steinar Bang
2014-03-20 20:39 ` Eli Zaretskii
2014-03-20 21:10 ` Steinar Bang
2014-03-21 7:46 ` Eli Zaretskii
2014-03-21 12:40 ` Stefan
2014-03-21 12:57 ` Steinar Bang
2014-03-21 16:08 ` Eli Zaretskii
2014-03-21 17:02 ` David Kastrup
2014-03-21 18:35 ` Eli Zaretskii
2014-03-21 19:01 ` David Caldwell
2014-03-20 16:17 ` Eli Zaretskii
2014-03-20 19:28 ` Óscar Fuentes
2014-03-20 20:19 ` Eli Zaretskii
2014-03-20 20:31 ` Óscar Fuentes
2014-03-20 20:40 ` Eli Zaretskii
2014-03-20 20:46 ` Óscar Fuentes
2014-03-21 3:02 ` Stephen J. Turnbull
2014-03-21 8:01 ` Eli Zaretskii
2014-03-22 7:18 ` Stefan-W. Hahn
2014-03-19 21:25 ` Andreas Schwab
2014-03-20 3:49 ` Eli Zaretskii
2014-03-20 7:46 ` Steinar Bang
2014-03-20 16:09 ` Glenn Morris
2014-03-20 20:17 ` Steinar Bang
2014-03-20 20:21 ` Eli Zaretskii
2014-03-20 16:33 ` Eli Zaretskii
2014-03-20 21:00 ` Steinar Bang
2014-03-21 9:08 ` Eli Zaretskii
2014-03-21 9:38 ` Andreas Schwab
2014-03-21 9:53 ` Steinar Bang
2014-03-21 10:17 ` Eli Zaretskii [this message]
2014-03-21 12:30 ` Steinar Bang
2014-03-20 18:19 ` Andreas Schwab
2014-03-20 18:27 ` Eli Zaretskii
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83mwgj6eld.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=sb@dod.no \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.