From: Junio C Hamano <gitster@pobox.com>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: Martin Langhoff <martin.langhoff@gmail.com>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: Grafts workflow for a "shallow" repository...?
Date: Mon, 15 Sep 2008 23:25:10 -0700 [thread overview]
Message-ID: <7v3ak08v5l.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <20080916052425.GA14644@spearce.org> (Shawn O. Pearce's message of "Mon, 15 Sep 2008 22:24:25 -0700")
"Shawn O. Pearce" <spearce@spearce.org> writes:
> Martin Langhoff <martin.langhoff@gmail.com> wrote:
>> Here is my attempt at a "let's publish a shallow repository for branch
>> of moodle". Let me show you what I did...
> ...
>> # 1.7 was a significant release, anything earlier than that
>> # is just not interesting -- even for pickaxe/annotate purposes
>> # so add a graft point right at the branching point.
> ...
>> Is this kind of workflow (or a variation of it) supported? For this to
>> work, we should communicate the grafts in some push operations and
>> read them in clone ops - and perhaps in fetch too.
> ...
> I think that in this case the best thing to do is give users
> a shell script that does roughly:
>
> git init
> echo $BASE >.git/info/grafts
> git remote add -f origin $url
> git checkout -b master origin/master
>
> Sign the script, and let users verify it before executing. You may
> also want a script to drag in the history behind by removing the
> graft and fetching $BASE^, but that is hard because your repository
> already "has" that.
Why not just filter-branch _once at the origin_ and publish the result?
next prev parent reply other threads:[~2008-09-16 6:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-16 5:09 Grafts workflow for a "shallow" repository...? Martin Langhoff
2008-09-16 5:24 ` Shawn O. Pearce
2008-09-16 6:25 ` Junio C Hamano [this message]
2008-09-16 8:09 ` Björn Steinbrink
2008-09-16 13:27 ` Michael J Gruber
2008-09-16 13:50 ` Björn Steinbrink
2008-09-16 22:02 ` Sverre Rabbelier
2008-09-16 23:12 ` Dmitry Potapov
2008-09-16 19:12 ` Grafts workflow for a Sergio
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=7v3ak08v5l.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=martin.langhoff@gmail.com \
--cc=spearce@spearce.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).