From: Jonathan Nieder <jrnieder@gmail.com>
To: Joey Hess <joey@kitenet.net>
Cc: GIT Mailing-list <git@vger.kernel.org>,
Johan Herland <johan@herland.net>
Subject: Re: git-union-merge proposal
Date: Tue, 21 Jun 2011 00:22:34 -0500 [thread overview]
Message-ID: <20110621052211.GA16919@elie> (raw)
In-Reply-To: <20110621022049.GA1632@gnu.kitenet.net>
Hi Joey,
Joey Hess wrote[1]:
> * git-annex stores location tracking information to log files in
> .git-annex/; gitattributes is configured to use merge=union,
> and the log files have timestamps or are otherwise structured to be
> safely merged.
> * git notes merge -s cat_sort_uniq
> Notes are stored in a tree using the object sha, which can be
> union merged, when the notes' format is a series of independant lines.
> * probably other tools do things like this too, or will ...
>
> So I've written a prototype of a git-union-merge that could be used
> for all of these. It works like this:
>
> git union-merge foo origin/foo refs/heads/foo
Hm, this makes a lot of sense. Often a person needs a worktree anyway
to check the merge result for sanity, but as you say, that needn't
always be the case.
[...]
> Prototype is attached, I doubt it would be suitable for git as-is,
Does the GitRepo module that it uses come from git-annex?
If the prototype were self-contained, I would encourage you to submit
it for inclusion under contrib/ so it can evolve and eventually
graduate out of there. Cc-ing Johan (who has no doubt thought through
these things in the context of "git notes") in case he has thoughts on
it.
Regards,
Jonathan
[1] http://thread.gmane.org/gmane.comp.version-control.git/176119
next prev parent reply other threads:[~2011-06-21 5:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-21 2:20 git-union-merge proposal Joey Hess
2011-06-21 5:22 ` Jonathan Nieder [this message]
2011-06-21 7:34 ` Johan Herland
2011-06-21 16:10 ` Joey Hess
2011-06-21 17:44 ` Junio C Hamano
2011-06-21 18:12 ` Junio C Hamano
2011-06-21 18:41 ` Joey Hess
2011-06-21 20:19 ` Junio C Hamano
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=20110621052211.GA16919@elie \
--to=jrnieder@gmail.com \
--cc=git@vger.kernel.org \
--cc=joey@kitenet.net \
--cc=johan@herland.net \
/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).