From: "Shawn O. Pearce" <spearce@spearce.org>
To: Martin Koegler <mkoegler@auto.tuwien.ac.at>
Cc: git@vger.kernel.org
Subject: Re: git-gui Error
Date: Wed, 14 Feb 2007 01:00:41 -0500 [thread overview]
Message-ID: <20070214060041.GA31871@spearce.org> (raw)
In-Reply-To: <20070214022200.GB30884@spearce.org>
"Shawn O. Pearce" <spearce@spearce.org> wrote:
> Martin Koegler <mkoegler@auto.tuwien.ac.at> wrote:
> > * It there any reason, why tags are not included in the list of possible
> > merge sources in Merge/Local Merge?
> >
> > It only needs one additional line in do_local_merge:
> > set cmd [list git for-each-ref]
> > lappend cmd {--format=%(objectname) %(refname)}
> > lappend cmd refs/heads
> > lappend cmd refs/remotes
> > + lappend cmd refs/tags
> > set fr_fd [open "| $cmd" r]
>
> I just didn't consider it. The way I use git-gui for merges, I never
> merge tags. But its obviously valid in plain Git. I'll add it.
This is now pushed to repo.or.cz. It probably won't show up in
git.git for at least a few weeks. I want to push through some
more features (especially around the blame UI) in git-gui before
I bother Junio with another git-gui merge. Besides, Git 1.5.0
(including git-gui 0.6.0.1) just shipped. :)
It turned out to be slightly more difficult than just adding
refs/tags, as %(objectname) would be the name of the annotated tag,
and we need the commit name to match against rev-list output. So I
had to extend the for-each-ref call to also include %(*objectname).
--
Shawn.
next prev parent reply other threads:[~2007-02-14 6:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-13 6:56 git-gui Error Martin Koegler
2007-02-13 7:45 ` Shawn O. Pearce
2007-02-13 21:53 ` Martin Koegler
2007-02-14 2:22 ` Shawn O. Pearce
2007-02-14 6:00 ` Shawn O. Pearce [this message]
2007-02-14 17:46 ` Martin Koegler
2007-02-15 2:40 ` Shawn O. Pearce
2007-02-15 6:07 ` Martin Koegler
2007-02-15 6:38 ` Shawn O. Pearce
2007-02-14 18:09 ` Martin Koegler
2007-02-15 4:07 ` Shawn O. Pearce
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=20070214060041.GA31871@spearce.org \
--to=spearce@spearce.org \
--cc=git@vger.kernel.org \
--cc=mkoegler@auto.tuwien.ac.at \
/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).