'bzr diff' should include file revision numbers
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bazaar |
Confirmed
|
Low
|
Unassigned | ||
Breezy |
Triaged
|
Low
|
Unassigned |
Bug Description
In Bugzilla, we have a feature which displays a patch with any given number of context lines, independently of the original number of context lines included in the patch (usually 3). For patches generated by 'cvs diff' we do this thanks to the revision number of the files included in the patch, and then get the files with these specific revision numbers. When the patch is generated using 'bzr diff', no revision number is included in the patch:
=== modified file 'process_bug.cgi'
--- process_bug.cgi 2007-10-12 07:21:59 +0000
+++ process_bug.cgi 2007-11-25 18:58:35 +0000
@@ -1223,6 +1223,10 @@
....
This means we have no easy way to know which revision numbers the patch was generated against and this makes us hard to know which original files to download (a workaround is to use the timestamp included in the headers, and to do a 'bzr cat -r date:', but that's not ideal). To be able to handle patches generated by Bazaar the same way as we do with CVS, we need this information by default when a patch is generated by 'bzr diff'.
Changed in brz: | |
status: | New → Triaged |
importance: | Undecided → Low |
tags: | added: diff |
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Frédéric Buclin wrote:
> Public bug reported:
>
> In Bugzilla, we have a feature which displays a patch with any given
> number of context lines, independently of the original number of context
> lines included in the patch (usually 3). For patches generated by 'cvs
> diff' we do this thanks to the revision number of the files included in
> the patch, and then get the files with these specific revision numbers.
> When the patch is generated using 'bzr diff', no revision number is
> included in the patch:
>
> === modified file 'process_bug.cgi'
> --- process_bug.cgi 2007-10-12 07:21:59 +0000
> +++ process_bug.cgi 2007-11-25 18:58:35 +0000
> @@ -1223,6 +1223,10 @@
> ....
>
> This means we have no easy way to know which revision numbers the patch
> was generated against and this makes us hard to know which original
> files to download (a workaround is to use the timestamp included in the
> headers, and to do a 'bzr cat -r date:', but that's not ideal). To be
> able to handle patches generated by Bazaar the same way as we do with
> CVS, we need this information by default when a patch is generated by
> 'bzr diff'.
>
It might be reasonable to add this as 'bzr diff --show-ids', which is
how some of the other commands deal with this.
John
=:->
-----BEGIN PGP SIGNATURE----- enigmail. mozdev. org/
KUk4ACgkQJdeBCY SNAAN2sACfe6RqZ RRwCjN+ xYcd4wVRfIu1 joDgMmfjxY6Lpnl gV
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://
iEYEARECAAYFAkr
Z+IAn3RU215xK5S
=nHy3
-----END PGP SIGNATURE-----