git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jan Harkes <jaharkes@cs.cmu.edu>
To: git@vger.kernel.org
Cc: Petr Baudis <pasky@ucw.cz>, Andrew Morton <akpm@osdl.org>
Subject: Re: I'm missing isofs.h
Date: Wed, 27 Apr 2005 12:43:51 -0400	[thread overview]
Message-ID: <20050427164351.GA7070@delft.aura.cs.cmu.edu> (raw)
In-Reply-To: <20050427135840.GE3014@pasky.ji.cz>

On Wed, Apr 27, 2005 at 03:58:41PM +0200, Petr Baudis wrote:
> Dear diary, on Wed, Apr 27, 2005 at 02:58:44PM CEST, I got a letter
> where Jan Harkes <jaharkes@cs.cmu.edu> told me that...
> > On Tue, Apr 26, 2005 at 09:43:38PM -0700, Andrew Morton wrote:
> > > In a current tree, using git-pasky-0.7:
> > 
> > It looks like git-pasky-0.7 doesn't include the following commit, but
> > there are also several other diff and merge related fixes that were
> > added since then.
> 
> Why do you think it doesn't include it? I can see the fix in the code.

I looked through the output of cg-log, which I thought had at least some
ordering, and that commit showed up as more recent than the pasky-0.7
entry. It looks like the same change is also part of pasky-0.7, but with
a different commit-id. Sorry about the confusion.

In any case, when I use
    cg-diff -r a2755a80f40e5794ddc20e00f781af9d6320fafb: | grep isofs.h

the missing file does show up,
    ...
    Index: fs/isofs/isofs.h
    +++ fd1621a8c03331bd78abfe52c8c385977d0a9729/fs/isofs/isofs.h (mode:100644 sha1:9ce7b51fb6141ea6b82d85687d490c74755591fb)
    ...

so either I'm missing some subtle command line error (missing ':' after
the tag-id?) or the problem was fixed by some other change. So I looked
through the logs to see if there was anything obvious and the commit I
mentioned looked promising.

Jan


  reply	other threads:[~2005-04-27 16:38 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-27  4:43 I'm missing isofs.h Andrew Morton
2005-04-27 12:58 ` Jan Harkes
2005-04-27 13:58   ` Petr Baudis
2005-04-27 16:43     ` Jan Harkes [this message]
2005-04-27 16:45       ` Jan Harkes
2005-04-27 15:31 ` Steven Cole
2005-04-27 17:40   ` Steven Cole
2005-04-27 23:51 ` Petr Baudis
2005-04-28  0:19   ` Linus Torvalds
2005-04-28  0:32     ` Petr Baudis
2005-04-28  2:02       ` Junio C Hamano
2005-04-28  5:27       ` Junio C Hamano
2005-04-28  6:28         ` [PATCH] Make diff-cache and friends output more cg-patch friendly Junio C Hamano
2005-04-28  7:52         ` I'm missing isofs.h Petr Baudis
2005-04-28 23:39           ` David A. Wheeler
2005-04-28 14:42         ` Linus Torvalds
2005-04-28 16:11           ` Junio C Hamano
2005-04-28 16:28             ` Linus Torvalds
2005-04-28  0:32   ` Cogito nit: cg-update should default to "origin" David A. Wheeler
2005-04-28  0:53     ` Petr Baudis
2005-04-28  1:52       ` Dan Holmsand
2005-04-28  3:57       ` David A. Wheeler
2005-04-28  8:22         ` Dan Holmsand

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=20050427164351.GA7070@delft.aura.cs.cmu.edu \
    --to=jaharkes@cs.cmu.edu \
    --cc=akpm@osdl.org \
    --cc=git@vger.kernel.org \
    --cc=pasky@ucw.cz \
    /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).