From: Jakub Narebski <jnareb@gmail.com>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 2/2] gitweb: New improved formatting of chunk header in diff
Date: Wed, 8 Nov 2006 22:55:03 +0100 [thread overview]
Message-ID: <200611082255.03617.jnareb@gmail.com> (raw)
In-Reply-To: <7vzmb1r4yu.fsf@assigned-by-dhcp.cox.net>
Junio C Hamano wrote:
> Jakub Narebski <jnareb@gmail.com> writes:
>
>> O.K. This one introduced new feature, and wasn't needed for earlier
>> accepted patch (output empty patches) to have sense. And it is rc1
>> phase...
>
> I personally do not mind minor gitweb 'feature' updates in -rc
> cycle, just like I am planning to see if there are gitk updates
> I haven't pulled from Paulus (I think there is at least one
> patch from last month or so), unless the changes do not break it
> so badly.
I'll resend corrected patch then...
>> By the way, where I can find proper specifiction of unified diff format?
>> Do I understand correctly that bot from and to ranges can be without
>> number of lines part if it simplifies to 0?
>
> When Linus did apply.c and I did diff.c, we primarily worked off
> of sources to GNU patch.
>
> There is a POSIX draft proposal now.
>
> http://www.opengroup.org/austin/mailarchives/ag-review/msg02077.html
>
> See also updates about the proposal.
>
> http://thread.gmane.org/gmane.comp.version-control.git/29331/focus=29389
Thanks a lot.
Personally I think that we should push for git extended headers to be
(as an option) in POSIX for unifed diff... well, with the exception
of index and similarity lines. ;-)
--
Jakub Narebski
next prev parent reply other threads:[~2006-11-08 21:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-08 10:47 [PATCH 0/2] Better unquoting of git quoted filenames; esc_path to escape pathnames for display Jakub Narebski
2006-11-08 10:48 ` [PATCH 1/2] gitweb: Better git-unquoting and gitweb-quoting of pathnames Jakub Narebski
2006-11-08 10:50 ` [PATCH 2/2] gitweb: Use character or octal escape codes (and add span.cntrl) in esc_path Jakub Narebski
2006-11-08 16:58 ` [PATCH 0/2] gitweb: New improved patchset view Jakub Narebski
2006-11-08 16:59 ` [PATCH 1/2] " Jakub Narebski
2006-11-08 18:27 ` Junio C Hamano
2006-11-08 18:57 ` Junio C Hamano
2006-11-08 19:04 ` Jakub Narebski
2006-11-08 18:41 ` [PATCH 1/2 (amend)] " Jakub Narebski
2006-11-08 17:00 ` [PATCH 2/2] gitweb: New improved formatting of chunk header in diff Jakub Narebski
2006-11-08 20:41 ` Junio C Hamano
2006-11-08 20:58 ` Jakub Narebski
2006-11-08 21:41 ` Junio C Hamano
2006-11-08 21:55 ` Jakub Narebski [this message]
2006-11-08 18:24 ` [PATCH 2/2] gitweb: Use character or octal escape codes (and add span.cntrl) in esc_path Junio C Hamano
2006-11-08 18:56 ` Jakub Narebski
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=200611082255.03617.jnareb@gmail.com \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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).