Quotation；東莞/深圳/廣州/中山/香港物流

Dear Sir/Miss This is the e-mail from Paul of HAOCHING INT'L LOGISTICS LTD in China. Our company is a well-staffed freight forwarding and logistics service company located in Shenzhen/Dongguan/Guangzhou/HuiZhou/Zhongshan GuangDong Province china，and provide safety, convenient and speedy

Re: Finding a commit based on the diff index line?

From: Junio C Hamano Sent: Saturday, September 17, 2016 5:30 PM Does it count as simple to use pager's search feature in "log --raw" output piped to it? Pardon typos & html; typed on a phone The `log --raw` looks useful, though I think (IIUC) I also have a problem that (obviously?) these

Re: Why are there multiple ways to get the manual in Git?

On Sat, Sep 17, 2016 at 8:39 PM, Fredrik Gustafsson wrote: > On Sat, Sep 17, 2016 at 01:47:52PM -0400, Andrew Johnson wrote: >> $ git help >> $ git --help >> $ man git- >> >> I tested all three to confirm they were equivalent. Maybe it will be easier to understand if you try:

Re: Why are there multiple ways to get the manual in Git?

From: "Fredrik Gustafsson" On Sat, Sep 17, 2016 at 01:47:52PM -0400, Andrew Johnson wrote: $ git help $ git --help $ man git- I tested all three to confirm they were equivalent. It is (IIUC) in a general sort of way "by design", and a little bit of accident. While

Re: [PATCH v2] format-patch: Add --rfc for the common case of [RFC PATCH]

On Sat, Sep 17, 2016 at 12:21:52AM -0700, Josh Triplett wrote: > This provides a shorter and more convenient alias for > --subject-prefix='RFC PATCH'. > > Includes documentation in the format-patch manpage, and a new test > covering --rfc. > > Signed-off-by: Josh Triplett

Re: Why are there multiple ways to get the manual in Git?

On Sat, Sep 17, 2016 at 01:47:52PM -0400, Andrew Johnson wrote: > $ git help > $ git --help > $ man git- > > I tested all three to confirm they were equivalent. While I'm not able to answer your question, I can shred a little light about them not being equal. For example using a windows

Re: Two bugs in --pretty with %C(auto)

Am 17.09.2016 um 14:51 schrieb Anatoly Borodin: > Hi All! > > First bug: > > git log -3 --pretty='%C(cyan)%C(auto)%h%C(auto)%d %s' > > prints %h with the default color (normal yellow), but > > git log -3 --pretty='%C(bold cyan)%C(auto)%h%C(auto)%d %s' > > shows %h with bold

Why are there multiple ways to get the manual in Git?

Hi, I was curious as to why the developers of Git decided to have three methods to get the manual for a verb. I am a developer who strives to understand Git to its fullest extent, and will share any information given on this question. While reading Pro Git 2nd Ed. I came across these three

Re: [wishlist] disable boring messages

Hi! Alexander Inyukhin wrote: > I have a lot of repos and a batch script to update them all, > and I want to get rid of 'Fetching origin' and 'Already up-to-date.' > messages leaving only new refs and tags. There is an option `-q`, but it's too silent :) As far as I can

Finding a commit based on the diff index line?

Hi, I'm curating some of my old patch series (i.e. doing some tidying up) and I'm trying to determine the commits that generated some of my patches so that I can see if I still have them after they were rebased (a 'name that dangling branch' problem). Is there an easy way of finding the

Two bugs in --pretty with %C(auto)

Hi All! First bug: git log -3 --pretty='%C(cyan)%C(auto)%h%C(auto)%d %s' prints %h with the default color (normal yellow), but git log -3 --pretty='%C(bold cyan)%C(auto)%h%C(auto)%d %s' shows %h with bold yellow, as if only the color was reset, but not the attributes (blink,

Re: Potentially misleading color.* defaults explanation in git-config(1)

Hi! Matthieu Moy wrote: > My bad, I forgot to update these parts of the docs when changing the > default for color.ui (a while back already). Patch follows. Thanks for the patch! > git -c color.branch=false git branch Oh, that's a nice one! I don't get a chance

[PATCH v2] format-patch: Add --rfc for the common case of [RFC PATCH]

This provides a shorter and more convenient alias for --subject-prefix='RFC PATCH'. Includes documentation in the format-patch manpage, and a new test covering --rfc. Signed-off-by: Josh Triplett --- v2: - Add documentation to the format-patch manpage - Call