[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Git transition checklist
From: |
Stefan Monnier |
Subject: |
Re: Git transition checklist |
Date: |
Thu, 09 Jan 2014 10:12:33 -0500 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/24.3.50 (gnu/linux) |
> Option 1 is like a regular bzr branch: branch1's history is identical
> to trunk up to the point of cloning, after that independent of trunk.
W.r.t to Bzr's shared repository, this is different in that the sharing
is asymmetric: what you pull into "trunk" will also be available
(without re-fetching) in ws1 but not vice-versa.
Also, this comes with a big "NOTE: this is a possibly dangerous operation"
in the manpage, because "trunk" doesn't know about "ws1", so a "git gc"
in trunk (explicit or implicit) may remove revisions that are still
needed by ws1.
Bzr avoided the problem by not providing "gc".
> For more glitches, ask Stefan.
I think that covers it up. Basically, IIUC, the rule for
git-new-workdir is "at most one workdir for a given branch".
So if you want a "second workdir" of trunk, make a new branch off of
"trunk" and then do a "new-workdir" for that new branch.
Stefan
- Re: Git transition checklist, (continued)
- Re: Git transition checklist, Eli Zaretskii, 2014/01/11
- Re: Git transition checklist, Glenn Morris, 2014/01/11
- Re: Git transition checklist, David Kastrup, 2014/01/11
- Re: Git transition checklist, Jorgen Schaefer, 2014/01/12
- Re: Git transition checklist, Barry Warsaw, 2014/01/13
- Re: Git transition checklist, Glenn Morris, 2014/01/13
- Re: Git transition checklist, David Kastrup, 2014/01/13
- Re: Git transition checklist, Richard Stallman, 2014/01/14
- Re: Git transition checklist,
Stefan Monnier <=
- Re: Git transition checklist, Andreas Schwab, 2014/01/09
Re: Git transition checklist, Eli Zaretskii, 2014/01/08
Re: Git transition checklist, Andreas Schwab, 2014/01/08
Re: Git transition checklist, Achim Gratz, 2014/01/08