From: "Tjernlund" <tjernlund@tjernlund.se>
To: "'Jakub Narebski'" <jnareb@gmail.com>
Cc: "'git'" <git@vger.kernel.org>
Subject: RE: gitweb improvements
Date: Tue, 7 Oct 2008 00:17:00 +0200 [thread overview]
Message-ID: <013b01c92801$40f5f8f0$c2e1ead0$@se> (raw)
In-Reply-To: <200810060154.06934.jnareb@gmail.com>
> -----Original Message-----
> From: Jakub Narebski [mailto:jnareb@gmail.com]
> Sent: den 6 oktober 2008 01:54
> To: Tjernlund
> Cc: 'git'
> Subject: Re: gitweb improvements
>
> On Mon, 6 Oct 2008, Tjernlund wrote:
> > Jakub Narebski wrote:
> >> "Tjernlund" <tjernlund@tjernlund.se> writes:
>
> >>> 2) looking at a merge like:
> >>> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-
> 2.6.git;a=commit;h=66120005e65eed8a05b14a36ab448bdec42f0d6b
> >>> is somewhat confusing. It really doesn't tell you which commits that is
> >>> included in the merge.
> >>
> >> I don't understand you there. First, you have "(merge: 0d0f3ef 9778e9a)"
> >> in the navbar, so you can easily go to commit view for parents. Second,
> >> among commit headers you have two "parent", where SHA-1 of a commit is
> >> hidden link, and there are also 'commit' and 'diff' link for those.
> >
> > hmm, looks like I overlooked "(merge: 0d0f3ef 9778e9a)" part. However, I can't
> > find the "ALSA: make the CS4270 driver a new-style I2C driver" from within
> > this page.
>
> I think you don't quite understand the situation. The history looks
> like this:
>
> M Merge branch 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound-2.6
> |\
> | 2 ALSA: ASoC: Fix another cs4270 error path
> | * ALSA: make the CS4270 driver a new-style I2C driver
> | |
> 1 | Merge git://git.kernel.org/pub/scm/linux/kernel/git/jejb/scsi-rc-fixes-2.6
>
> Parents of commit 'M' (for merge) are '1' and '2', not 2,* or 1,2,*.
>
> Now the fact that commit message for merge contains shortlog of merged
> branch does not mean that there must be direct link to such shortlog.
> You can go to shortlog (well, kind of) if you click on second parent,
> _then_ click on shortlog link at top of the page.
You are quite right, I didn't quite follow the situation. I do however have one
observation, would it be possible to list the commits in a merge the same way
you list commits on the top level, that is, more or less make the headings
"ALSA: ASoC: Fix another cs4270 error path"
"ALSA: make the CS4270 driver a new-style I2C driver"
links one can follow?
Jocke
prev parent reply other threads:[~2008-10-06 22:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-05 15:45 gitweb improvements Tjernlund
2008-10-05 17:22 ` Jakub Narebski
2008-10-05 22:25 ` Tjernlund
2008-10-05 23:54 ` Jakub Narebski
2008-10-06 22:17 ` Tjernlund [this message]
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='013b01c92801$40f5f8f0$c2e1ead0$@se' \
--to=tjernlund@tjernlund.se \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.com \
/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).