[pacman-dev] [GIT] pacman branch, master now at v3.0.0-410-g7325ebb

Dan McGee dpmcgee at gmail.com
Tue Sep 18 07:44:06 EDT 2007

On 9/18/07, Roman Kyrylych <roman.kyrylych at gmail.com> wrote:
> 2007/9/18, Dan McGee <dan at archlinux.org>:
> > Hello,
> >
> > This is an automated email from the git hooks/update script, it was
> > generated because a ref change was pushed to the repository.
> >
> hmm, I cannot see most of these changes in shortlog.
> I guess the changes that was made in a (asciidoc) branch don't show up
> in master summary/shortlog.
> But it *seems* that git on kernel.org does this (which is good, IMO,
> for tracking changes for adding to NEWS file).
> Is there way to get the same behaviour in pacman git.
> I'm not expert in git so sorry if what I'm saying is stupid. :-P

They are there. By default GIT outputs its log entries in
chronological order. Topological order makes more sense for a case
like this.

You'd have to search Google for the myriad of git-log options.


More information about the pacman-dev mailing list