On 2015-11-03 02:22, Vadim A. Misbakh-Soloviov wrote: > Actually, git log understands if you specify path for it (especially > after --)... > > > 03.11.2015 02:05, Daniel Campbell пишет: > > On 11/01/2015 04:22 AM, Anthony G. Basile wrote: > > > On 11/1/15 7:16 AM, Patrick Lauer wrote: > > >> Ahoi, > > >> > > >> I'm getting mildly very irritated with the lack of easily > > >> accessible ChangeLogs for our packages. > > >> > > >> Apparently updating them stopped some time in August, so now > > >> there are some outdated ChangeLogs that don't really serve any > > >> purpose, and the easiest way for users to figure out why > > >> something changed is to yell at the clumsy gitweb.g.o interface. > > >> So instead of grep we now need lots of patience. > > >> > > >> This does not look reasonable to me. > > >> > > >> Can we please either properly remove ChangeLogs and tell people > > >> to not be curious about changes, or make them useful again? > > >> > > >> Thanks, > > >> > > >> A Gentoo User. > > >> > > > I don't have strong feelings about this, but I'm happy with `git > > > log` to tell me what's going on with packages. I would be okay > > > with the ChangeLog files just being archived and removed. > > > > > > Is there a way for us (devs and users both) to only get `git log` > > results from a specific directory or package? I'm aware we could pipe > > git log to grep, but that seems hackish, like git has a better way to > > isolate log entries. > > > > > >
Vadim, please don't top post.
Daniel, yes, you just do:
git log cat/pkg
Or:
git log .
`git log' understands path arguments within the repo.
But, that doesn't really give you the full picture. You will be better
served by:
git log --grep=<pattern>
signature.asc
Description: Digital signature
