Re: [PATCH 9/9] trailer: add tests for "git interpret-trailers"
On Mon, Dec 30, 2013 at 01:05:25PM -0800, Junio C Hamano wrote: > Josh Triplett writes: > >> - With your scheme, if you already had _one_ trailing SPs in the > >>input, it would be hard to spot in the source; > > > > Git makes them quite difficult to miss. :) > > That is irrelevant, isn't it? > > This is about protecting the source in the editor, before you run > "git show --whitespace=trailing-space", "git diff --check", etc. That was exactly my point: such lines shouldn't exist, and rather than including the trailing space and following it with a character that then needs removing, it seems more sensible to me to omit the trailing space and insert it via an almost identical sed line. Git already helps ensure that trailing space won't exist on *any* line, including those; I don't see how an extra character after the space (making it no longer trailing space) makes it any more or less likely that those lines would have trailing space. In any case, I don't care enough to argue the point further; it was just a style suggestion. - Josh Triplett -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH 9/9] trailer: add tests for "git interpret-trailers"
Josh Triplett writes: >> - The "everybody will have a single SP at the end" may or may not >>last forever; > > Trivially fixed if that ever changes, but given the nature of all of > these, that seems unlikely. Why? Because we encourage to write tests that are expected to find breakages, some of these test vector lines may have to show a broken line that lacks SP after label + colon. >> - With your scheme, if you already had _one_ trailing SPs in the >>input, it would be hard to spot in the source; > > Git makes them quite difficult to miss. :) That is irrelevant, isn't it? This is about protecting the source in the editor, before you run "git show --whitespace=trailing-space", "git diff --check", etc. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH 9/9] trailer: add tests for "git interpret-trailers"
On Mon, Dec 30, 2013 at 12:46:33PM -0800, Junio C Hamano wrote: > Josh Triplett writes: > > > On Mon, Dec 30, 2013 at 09:19:55AM -0800, Junio C Hamano wrote: > >> Christian Couder writes: > >> > >> > +# Do not remove trailing spaces below! > >> > +cat >complex_message_trailers <<'EOF' > >> > +Fixes: > >> > +Acked-by: > >> > +Reviewed-by: > >> > +Signed-off-by: > >> > +EOF > >> > >> Just a hint. I think it is far safer and robust over time to do > >> something like this: > >> > >>sed -e 's/ Z$/ /' <<-\EOF > >> Fixes: Z > >> Acked-by: Z > >> EOF > >> > >> instead of a comment, which can warn human developers but does not > >> do anything to prevent their editors' auto-fix features from kicking > >> in. > > > > This, but for simplicity, since every line needs the trailing space, why > > not just use 's/$/ /' and drop the ' Z' on every line? > > > > > > > > - Josh Triplett > > A few reasons: > > - The "everybody will have a single SP at the end" may or may not >last forever; Trivially fixed if that ever changes, but given the nature of all of these, that seems unlikely. > - With your scheme, if you already had _one_ trailing SPs in the >input, it would be hard to spot in the source; Git makes them quite difficult to miss. :) - Josh Triplett -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH 9/9] trailer: add tests for "git interpret-trailers"
Josh Triplett writes: > On Mon, Dec 30, 2013 at 09:19:55AM -0800, Junio C Hamano wrote: >> Christian Couder writes: >> >> > +# Do not remove trailing spaces below! >> > +cat >complex_message_trailers <<'EOF' >> > +Fixes: >> > +Acked-by: >> > +Reviewed-by: >> > +Signed-off-by: >> > +EOF >> >> Just a hint. I think it is far safer and robust over time to do >> something like this: >> >> sed -e 's/ Z$/ /' <<-\EOF >> Fixes: Z >> Acked-by: Z >> EOF >> >> instead of a comment, which can warn human developers but does not >> do anything to prevent their editors' auto-fix features from kicking >> in. > > This, but for simplicity, since every line needs the trailing space, why > not just use 's/$/ /' and drop the ' Z' on every line? > > > > - Josh Triplett A few reasons: - The "everybody will have a single SP at the end" may or may not last forever; - With your scheme, if you already had _one_ trailing SPs in the input, it would be hard to spot in the source; - It makes it visually very clear that we expect a SP after these colons. This is especially true if you replace 'Z' with something more readable (e.g. '|'). -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH 9/9] trailer: add tests for "git interpret-trailers"
On Mon, Dec 30, 2013 at 09:19:55AM -0800, Junio C Hamano wrote: > Christian Couder writes: > > > +# Do not remove trailing spaces below! > > +cat >complex_message_trailers <<'EOF' > > +Fixes: > > +Acked-by: > > +Reviewed-by: > > +Signed-off-by: > > +EOF > > Just a hint. I think it is far safer and robust over time to do > something like this: > > sed -e 's/ Z$/ /' <<-\EOF > Fixes: Z > Acked-by: Z > EOF > > instead of a comment, which can warn human developers but does not > do anything to prevent their editors' auto-fix features from kicking > in. This, but for simplicity, since every line needs the trailing space, why not just use 's/$/ /' and drop the ' Z' on every line? - Josh Triplett -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH 9/9] trailer: add tests for "git interpret-trailers"
Christian Couder writes: > +# Do not remove trailing spaces below! > +cat >complex_message_trailers <<'EOF' > +Fixes: > +Acked-by: > +Reviewed-by: > +Signed-off-by: > +EOF Just a hint. I think it is far safer and robust over time to do something like this: sed -e 's/ Z$/ /' <<-\EOF Fixes: Z Acked-by: Z EOF instead of a comment, which can warn human developers but does not do anything to prevent their editors' auto-fix features from kicking in. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html