From: Andy Parkins <andyparkins@gmail.com>
To: git@vger.kernel.org
Cc: Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: Bug: segfault during git-prune
Date: Fri, 29 Jun 2007 13:39:58 +0100 [thread overview]
Message-ID: <200706291340.00429.andyparkins@gmail.com> (raw)
In-Reply-To: <alpine.LFD.0.98.0706281525460.8675@woody.linux-foundation.org>
On Thursday 2007, June 28, Linus Torvalds wrote:
> On Thu, 28 Jun 2007, Andy Parkins wrote:
> > I had hoped that git-prune wouldn't be a risk because I have:
> >
> > * -- * -- * -- * -- * (ffmpeg-svn)
> >
> > * -- * -- * -- * (libswscale-svn)
>
> Ok. If all subproject branches are also visible in the superproject as
> refs, then "git prune" should work fine, and you can apply my patch and
> it should just work very naturally: the reachability analysis will find
> the subprojects not through the superproject link, but simply through the
> direct refs to the subproject.
Excellent. That's what I'd hoped.
I'm actually really impressed that git is robust enough that my symbolic
linking of all the .git subdirectories works so well. It's actually turned
out to be a really natural way of using a repository for strongly connected
submodules.
> This is not unlike just having two different repositories sharing the
> same object directory: as long as the two different repositories both
> have the appropriate refs, pruning is fine. In other words, you can see
> them as just independent branches in the same repo.
Absolutely. With my poor-mans submodule script that I was using before git
had it's own submodule support, I had the script make a refs/superrefs
directory, and every time I committed to the supermodule the script would
write $subhash to $submodule/.git/refs/heads/superrefs/$subhash. The it
was safe to git-prune the submodules as well.
> And in fact, subprojects are obviously very much *designed* to work that
> way: a subproject is basically a "different repository". So the basic
> rule is that if it would work with totally independent repos, it works
> with subprojects.
I certainly agree, it's an extremely elegant way of working. I can't
imagine that any other VCS is capable of this sort of manipulation.
> Anyway, if that patch works for you, I'd suggest you just pass it on to
> Junio (and feel free to add my "Signed-off-by:" on it - but conditional
> on you having actually tested it).
Will do. I'll certainly test it, and am happy to forward it on if that test
is successful.
Andy
--
Dr Andy Parkins, M Eng (hons), MIET
andyparkins@gmail.com
next prev parent reply other threads:[~2007-06-29 12:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-28 10:34 Bug: segfault during git-prune Andy Parkins
2007-06-28 10:52 ` Andy Parkins
2007-06-28 15:59 ` Linus Torvalds
2007-06-28 16:09 ` Linus Torvalds
2007-06-28 22:21 ` Andy Parkins
2007-06-28 22:31 ` Linus Torvalds
2007-06-29 12:39 ` Andy Parkins [this message]
2007-07-02 10:00 ` Andy Parkins
2007-07-02 11:45 ` Linus Torvalds
2007-07-02 13:25 ` Andy Parkins
2007-07-02 21:01 ` Linus Torvalds
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=200706291340.00429.andyparkins@gmail.com \
--to=andyparkins@gmail.com \
--cc=git@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).