From: Jakub Narebski <jnareb@gmail•com>
To: git@vger•kernel.org
Subject: Re: Creating diffs
Date: Thu, 03 Aug 2006 16:47:49 +0200 [thread overview]
Message-ID: <eat29j$lil$1@sea.gmane.org> (raw)
In-Reply-To: easqpi$o51$1@sea.gmane.org
Jakub Narebski wrote:
> Rocco Rutte wrote:
>
>> However, when I do:
>>
>> $ git diff source:file dest:file
>>
>> I get:
>>
>> --- a/source:file
>> +++ b/source:file
>>
>> But I'd like to drop the branchname. Can I do that without filtering
>> everything through sed(1)?
>
> If I remember correctly there were two patches which solved it
> differently:
>
> one gave
>
> --- a/source:file
> +++ b/dest:file
>
> second (and I guess it is better solution)
>
> --- a/file
> +++ b/file
>
> Unfortunately they seem unapplied...
The patches are:
http://www.gelato.unsw.edu.au/archives/git/0607/24325.html
http://www.gelato.unsw.edu.au/archives/git/0607/24326.html
--
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
next prev parent reply other threads:[~2006-08-03 14:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-03 12:29 Creating diffs Rocco Rutte
2006-08-03 12:39 ` Jakub Narebski
2006-08-03 14:47 ` Jakub Narebski [this message]
2006-08-03 14:58 ` Rocco Rutte
2006-08-03 18:45 ` Junio C Hamano
2006-08-03 18:22 ` Junio C Hamano
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='eat29j$lil$1@sea.gmane.org' \
--to=jnareb@gmail$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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