[no subject]

[ok]

--
ATTENTION
I want you to contact
Fast Courier Express & Logistics
so that swill send you the ATM card fast. mind you that as soon as you
received your ATM card you have to be taking 5000 dollars every day 
until the
total amount of your fund which is 3,8 million dollars okay contact
them they will also give you ,your
tracking so that you will know where your card is okay
Fast Courier Express & Logistics
Office Address: 223 CAVALRY
06 BP 700 Cotonou, Republic of Benin
E-mail: {fastercour...@yahoo.com}Website: www.fastcourierexpress.org
Telephone: +1(601)516-5047
THANK YOU


--

[no subject]

[Sherrone Delaney]

We need to make sure everyone's contact information is up to date,
please login with your corporate login and verify the information is correct:
Click here
We need to have this list updated within 24hrs, so please make this a priority.
Thank You

[no subject]

[Roya Moaddel]

We need to make sure everyone's contact information is up to date,
please login with your corporate login and verify the information is correct:
Click here
We need to have this list updated within 24hrs, so please make this a priority.
Thank You

[no subject]

[SZEDER Gábor]

On Tue, Nov 20, 2018 at 05:58:00PM +0100, SZEDER Gábor wrote:
> I saw a
> bit of weirdness while at it, and want to look into it, but now I've
> got to go...

So here are two simple patches that address the "Huh?!" moments I had
while looking at the progress output during writing the commit graph
file.  The first is a small cleanup to avoid confusion, but see the
notes attaches, while the second is a bit of an optimization.

SZEDER Gábor (2):
  commit-graph: rename 'num_extra_edges' variable to 'num_large_edges'
  commit-graph: don't call write_graph_chunk_large_edges() unnecessarily

 commit-graph.c | 21 +++--
 1 file changed, 11 insertions(+), 10 deletions(-)

-- 
2.20.0.rc0.134.gf0022f8e60

[no subject]

[Major Dennis Hornbeck]

I am in the military unit here in Afghanistan, we have some amount of funds 
that we want to move out of the country. My partners and I need a good partner 
someone we can trust. It is risk free and legal. Reply to this email: 
hornbeckmajordennis...@gmail.com
Regards,Major Dennis Hornbeck.

[no subject]

[Veronica Ali]

Dear friend,

I am very gald and happy that you answerred this message very fast, My
name is Veronica Ali. a France Nationality, I am a widow, currently
hospitalized due to cancer illness . Meanwhile, I have decided to
donate my fund to you as a reliable individual that will use this
money wisely, €3,800.000 Million Euros. to help the poor and less
privileged.

So if you are willing to accept this offer and do exactly as I will
instruct, then get back to me for more details.

Mrs Veronica Ali.

[no subject]

[Mihir Mehta]

Thanks, Junio. Instead of removing that part of the patch, I opted to
expand it to make it a little clearer (in my opinion) than it was
before. Let me know if this works.

Mihir.

[no subject]

[Netravnen]

unsubscribe git

Re: [PATCH v5 0/7] subject: Clean up tests for test_cmp arg ordering and pipe placement

[Junio C Hamano]

Matthew DeVore  writes:

> This version of the patchset fixes some wording and formatting issues
> pointed out by Junio. The commit message in the first patch has also
> been reworded.


Thanks.

If no further major issues are raised, let's merge it to 'next'.

[no subject]

[Major Dennis Hornbeck.]

I am in the military unit here in Afghanistan, we have some amount of funds 
that we want to move out of the country. My partners and I need a good partner 
someone we can trust. It is risk free and legal. Reply to this email: 
hornbeckmajorden...@gmail.com

Regards,
Major Dennis Hornbeck.

[PATCH v5 0/7] subject: Clean up tests for test_cmp arg ordering and pipe placement

[Matthew DeVore]

This version of the patchset fixes some wording and formatting issues
pointed out by Junio. The commit message in the first patch has also
been reworded.

Thank you,
Matt

diff --git a/t/README b/t/README
index 9a71d5732..ab9fa4230 100644
--- a/t/README
+++ b/t/README
@@ -394,7 +394,7 @@ This test harness library does the following things:
--debug (or -d), and --immediate (or -i) is given.
 
 Do's & don'ts
--
+-
 
 Here are a few examples of things you probably should and shouldn't do
 when writing tests.
@@ -466,8 +466,7 @@ And here are the "don'ts:"
platform commands; just use '! cmd'.  We are not in the business
of verifying that the world given to us sanely works.
 
- - Don't use Git upstream in the non-final position in a piped chain, as
-   in:
+ - Don't feed the output of a git command to a pipe, as in:
 
  git -C repo ls-files |
  xargs -n 1 basename |
diff --git a/t/t5616-partial-clone.sh b/t/t5616-partial-clone.sh
index eeedd1623..6ff614692 100755
--- a/t/t5616-partial-clone.sh
+++ b/t/t5616-partial-clone.sh
@@ -35,7 +35,7 @@ test_expect_success 'setup bare clone for server' '
 test_expect_success 'do partial clone 1' '
 git clone --no-checkout --filter=blob:none "file://$(pwd)/srv.bare" 
pc1 &&
 
-git -C pc1 rev-list --quiet --objects --missing=print >revs HEAD &&
+git -C pc1 rev-list --quiet --objects --missing=print HEAD >revs &&
 awk -f print_1.awk revs |
 sed "s/?//" |
 sort >observed.oids &&
@@ -93,8 +93,8 @@ test_expect_success 'verify diff causes dynamic object fetch' 
'
 test_expect_success 'verify blame causes dynamic object fetch' '
 git -C pc1 blame origin/master -- file.1.txt >observed.blame &&
 test_cmp expect.blame observed.blame &&
-git -C pc1 rev-list --quiet --objects --missing=print >observed \
-master..origin/master &&
+git -C pc1 rev-list --quiet --objects --missing=print \
+master..origin/master >observed &&
 test_line_count = 0 observed
 '
 

Matthew DeVore (7):
  t/README: reformat Do, Don't, Keep in mind lists
  Documentation: add shell guidelines
  tests: standardize pipe placement
  t/*: fix ordering of expected/observed arguments
  tests: don't swallow Git errors upstream of pipes
  t9109: don't swallow Git errors upstream of pipes
  tests: order arguments to git-rev-list properly

 Documentation/CodingGuidelines |  18 ++
 t/README   |  69 +++--
 t/lib-gpg.sh   |   9 +-
 t/t-basic.sh   |   2 +-
 t/t0021-conversion.sh  |   4 +-
 t/t1006-cat-file.sh|   8 +-
 t/t1300-config.sh  |   9 +-
 t/t1303-wacky-config.sh|   4 +-
 t/t2101-update-index-reupdate.sh   |   2 +-
 t/t3200-branch.sh  |   2 +-
 t/t3320-notes-merge-worktrees.sh   |   4 +-
 t/t3400-rebase.sh  |   8 +-
 t/t3417-rebase-whitespace-fix.sh   |   6 +-
 t/t3702-add-edit.sh|   4 +-
 t/t3903-stash.sh   |   8 +-
 t/t3905-stash-include-untracked.sh |   2 +-
 t/t4025-hunk-header.sh |   2 +-
 t/t4117-apply-reject.sh|   6 +-
 t/t4124-apply-ws-rule.sh   |  30 +--
 t/t4138-apply-ws-expansion.sh  |   2 +-
 t/t5317-pack-objects-filter-objects.sh | 360 ++---
 t/t5318-commit-graph.sh|   2 +-
 t/t5500-fetch-pack.sh  |   7 +-
 t/t5616-partial-clone.sh   |  50 ++--
 t/t5701-git-serve.sh   |  14 +-
 t/t5702-protocol-v2.sh |  14 +-
 t/t6023-merge-file.sh  |  12 +-
 t/t6027-merge-binary.sh|   4 +-
 t/t6031-merge-filemode.sh  |   2 +-
 t/t6112-rev-list-filters-objects.sh| 237 +---
 t/t7201-co.sh  |   4 +-
 t/t7406-submodule-update.sh|   8 +-
 t/t7800-difftool.sh|   2 +-
 t/t9100-git-svn-basic.sh   |   2 +-
 t/t9101-git-svn-props.sh   |  34 ++-
 t/t9133-git-svn-nested-git-repo.sh |   6 +-
 t/t9600-cvsimport.sh   |   2 +-
 t/t9603-cvsimport-patchsets.sh |   4 +-
 t/t9604-cvsimport-timestamps.sh|   4 +-
 39 files changed, 568 insertions(+), 399 deletions(-)

-- 
2.19.0.605.g01d371f741-goog

[no subject]

[SUMITOIMO]

--
Did you receive our proposal email ?

[no subject]

[FIGADERE, LAURENT]

Hi,

Coming back to you with some updates.

I understand finally interest of difference between 'from' and 'at'.

The point is: is it a bug if the 'git status' provide the origin/HEAD instead 
of HEAD SHA1? 

If you want a test case with screenshots, let me know.

Regards,
Laurent

_
From: FIGADERE, LAURENT 
Sent: Thursday, September 20, 2018 3:26 PM
To: 'git@vger.kernel.org' <mailto:git@vger.kernel.org>
Subject: git status - difference between from and at


Hi guys,

Recently I used git on a top repository which integrated few other submodules.

The 'git submodule' command provides the right information on SHA1 used for 
each submodule.
When I 'cd' into a submodule and run the command 'git status', I got this 
message:
HEAD detached from 55846b8
nothing to commit, working tree clean
Which was not the right checked out SHA1: it should be 2422597

I verified in a git log command, and I was using really the '2422597' SHA1 and 
not 55846b8.
The command: 
  git log --graph --oneline --abbrev-commit --all
Output:
*   55846b8 (tag: 01.050.002, origin/master, origin/HEAD, master) 
...
*   2422597 (HEAD)
...

After running :
git co master
cd ..
git submodule update

I ran again git status command inside the submodule.
This time, I got this message:
HEAD detached at 2422597
nothing to commit, working tree clean

First question: do you confirm that 'HEAD detached FROM' provides the SHA1 of 
origin/HEAD?
And 'HEAD detached AT' provides the SHA1 we are using : HEAD?

Second question: what is the goal of such information?
Because from my opinion it can be difficult for end users to understand what 
SHA1 they are using in the submodule.

Thanks by advance for you feedbacks.

Regards,
Laurent Figadere

Re: Subject: [PATCH 0/9] hdr-check

[Elijah Newren]

Hi Ramsay,

On Tue, Sep 18, 2018 at 5:09 PM Ramsay Jones
 wrote;
> This series follows on from a quick "just before bedtime" exercise
> recently[1]. The new 'hdr-check' target essentially automates what
> Elijah did by hand.

Cool, thanks for doing this.  I believe I only tried to directly check
the toplevel header files (any fixes I made to headers in
subdirectories were just due to their indirect inclusion), so it's not
surprising to see that you needed to fix up some headers in
subdirectories.  It is slightly surprising to me that we've already
gained 6 cases of toplevel header files that needed fixes; that
suggests this hdr-check is even more useful than I would have
suspected.

The Make-fu in patch 1 is beyond the make I know, but the other
patches are all pretty simple and look good to me.

Subject: [PATCH 0/9] hdr-check

[Ramsay Jones]

This series follows on from a quick "just before bedtime" exercise
recently[1]. The new 'hdr-check' target essentially automates what
Elijah did by hand. I tend to run:

  $ make -h hdr-check >hcout 2>&1
  $ vim hcout

... and I only just realised that if somebody wanted to add this to
an travis CI job (it won't be me), then it would be a good idea to
add '-Werror' to the compiler command; otherwise 'make' would not
exit with an error if the compiler only issues warnings.

This series was built on the current 'master' branch (@2d3b1c576c),
although patches #1-6 apply on v2.19.0. (The last three patches used
to be on 'next' until last night!).

If I merge this to 'next', I have to add an additional patch for a
clean 'hdr-check'. Exactly the same comment for the current 'pu'
branch.

[1] 
https://public-inbox.org/git/b8553a50-6b97-2b45-2f7b-cfe257654...@ramsayjones.plus.com/

ATB,
Ramsay Jones

Ramsay Jones (9):
  Makefile: add a hdr-check target
  json-writer.h: add missing include (hdr-check)
  ewah/ewok_rlw.h: add missing include (hdr-check)
  refs/ref-cache.h: add missing declarations (hdr-check)
  refs/packed-backend.h: add missing declaration (hdr-check)
  refs/refs-internal.h: add missing declarations (hdr-check)
  midx.h: add missing forward declarations (hdr-check)
  delta-islands.h: add missing forward declarations (hdr-check)
  commit-reach.h: add missing declarations (hdr-check)

 Makefile  | 12 
 commit-reach.h|  5 +++--
 delta-islands.h   |  4 
 ewah/ewok_rlw.h   |  2 ++
 json-writer.h |  2 ++
 midx.h|  3 +++
 refs/packed-backend.h |  2 ++
 refs/ref-cache.h  |  3 +++
 refs/refs-internal.h  |  4 
 9 files changed, 35 insertions(+), 2 deletions(-)

-- 
2.19.0

[no subject]

[iluminati]

-- 
join the Illuminati secret brotherhood and get $3,000,000.00

[no subject]

[iluminati]

-- 
join the Illuminati secret brotherhood and get $3,000,000.00

[no subject]

[Illuminati]

This is the great brotherhood Illuminati,Do you want to become rich and
famous contact us now

[no subject]

[Charity Bam]

Üdvözlet neked, a nevem Mrs. Charity Edward. egy francia
állampolgárság, özvegy vagyok, jelenleg kórházba került a rákbetegség
miatt. Közben úgy döntöttem, hogy pénzt adok neked mint egy megbízható
személy, aki ezt a pénzt bölcsen fogja felhasználni, 3 800 000 millió
eurót. segíteni a szegényeket és kevésbé kiváltságos.

Tehát ha hajlandóak vagyunk elfogadni ezt az ajánlatot, és pontosan
úgy, ahogy én utasítom, akkor további részletekért térjenek vissza
hozzám.

Mrs. Charity Edward Bam.

[no subject]

[Mr Arthur]

did you get my last letter?

[no subject]

[johpaulesq...@gmail.com]

Chúng tôi mang lại thông báo cho bạn rằng chính phủ của chúng tôi
chiến đấu cho những người lừa đảo bây giờ ở nước ta Togo và chính phủ
của chúng tôi IMF phát hiện ra địa chỉ email của bạn trong danh sách
nạn nhân lừa đảo ở nước ta Togo và từ bi tổng số của bạn $ 850;
000.00. Chúng tôi không thể chuyển tiền cho bạn qua địa chỉ email.

  Chúng tôi sẽ chuyển hàng ngày cho bạn $ 5000 thông qua văn phòng
ngân hàng gram tiền của chúng tôi cho đến khi quỹ chuyển hoàn toàn cho
bạn. Xin vui lòng nếu bạn không sẵn sàng để nhận được quỹ này, đừng
trả lời chúng tôi

Chúng tôi yêu cầu khi nào có thể chuyển tiền cho bạn

Tên đầy đủ của bạn
Địa chỉ nhà
Quốc gia / thành phố
Số điện thoại
Bản sao hộ chiếu

Chúng tôi mong được nghe từ bạn khẩn trương.

Trân trọng
  Mr.Felix Richard
  M.G GIÁM ĐỐC NGÂN HÀNG
Điện thoại: +22891368099

[no subject]

[Mr Richard]

-- 
I Mr Richard Wahl donates $ 2 Million Dollars from part of my $533M In Mega 
MillionsJackpot.WATCH ME HERE: https://www.youtube.com/watch?v=tne02ExNDrw
File for claims

[no subject]

[Mr.Manfred Robert]

Ich habe einen Wohltätigkeitsfonds für Sie im Wert von € 4,800,000. Diese 
Spende ist
für die ersten 5 Personen, die auf diese E-Mail antworten, die als Form von
Wohltätigkeitshäusern zu Ehren meiner verstorbenen Frau gegeben wird, die an 
Krebs
gestorben ist. Kontaktieren Sie meinen Anwalt über diese E-Mail, um Ihre Spende 
zu
erhalten: ( barrmichaelbrad...@legislator.com ) or 
(barr.michaelbrad...@gmail.com )

[no subject]

[Mr.Manfred Robert]

Ich habe einen Wohltätigkeitsfonds für Sie im Wert von € 4,800,000. Diese 
Spende ist
für die ersten 5 Personen, die auf diese E-Mail antworten, die als Form von
Wohltätigkeitshäusern zu Ehren meiner verstorbenen Frau gegeben wird, die an 
Krebs
gestorben ist. Kontaktieren Sie meinen Anwalt über diese E-Mail, um Ihre Spende 
zu
erhalten: ( barrmichaelbrad...@legislator.com ) or 
(barr.michaelbrad...@gmail.com )

[no subject]

[johnpaules...@gmail.com]

[no subject]

[johnpaules...@gmail.com]

[no subject]

[Sumitomo Rubber Industries]

--
We have been trying to reach you.

[no subject]

[oeplmktg]

[no subject]

[Ubaithullah Masood]

Could you act as the beneficiary to claim 9.8M USD that my bank wants
to confiscate? I will give you 50% and Every documentation would be
put in placed.
Mr Ubaithullah from Hong Kong.

[no subject]

[Joseph Obieke]

¿Todo lo que necesito es una persona honesta en quien pueda confiar?
¿Puedo confiar en que transfiera la suma de $ 12.500.000.00 millones
de dólares estadounidenses a su cuenta si es posible, contáctenos para
obtener más detalles a través de mi dirección de correo electrónico
privada jobiekeoff...@gmail.com
Trate muy urgente y confidencialmente con confianza y honestamente y
usted compartirá el fondo una vez que se transfiera a su cuenta porque
el gobierno está haciendo un avión para confiscar el fondo.
Esperando con urgencia para saber de ti.
Mr Joseph Obieke

subscription (was: (no subject))

[Eric Wong]

Daniel Villeneuve  wrote:
> subscribe

That line should be "subscribe git" and it needs to be
sent to majord...@vger.kernel.org , not this list.

[no subject]

[Daniel Villeneuve]

subscribe

[no subject]

[Elijah Newren]

From: Elijah Newren <new...@gmail.com>

On Thu, Apr 26, 2018 at 5:54 PM, Ben Peart <peart...@gmail.com> wrote:

> Can you write the documentation that clearly explains the exact behavior you
> want?  That would kill two birds with one stone... :)

Sure, something like the following is what I envision, and I've tried to
include the suggestion from Junio to document the copy behavior in the
merge-recursive documentation.

-- 8< --
Subject: [PATCH] fixup! merge: Add merge.renames config setting

---
 Documentation/merge-config.txt | 3 +--
 Documentation/merge-strategies.txt | 5 +++--
 merge-recursive.c  | 8 
 3 files changed, 12 insertions(+), 4 deletions(-)

diff --git a/Documentation/merge-config.txt b/Documentation/merge-config.txt
index 59848e5634..662c2713ca 100644
--- a/Documentation/merge-config.txt
+++ b/Documentation/merge-config.txt
@@ -41,8 +41,7 @@ merge.renameLimit::
 merge.renames::
Whether and how Git detects renames.  If set to "false",
rename detection is disabled. If set to "true", basic rename
-   detection is enabled.  If set to "copies" or "copy", Git will
-   detect copies, as well.  Defaults to the value of diff.renames.
+   detection is enabled.  Defaults to the value of diff.renames.
 
 merge.renormalize::
Tell Git that canonical representation of files in the
diff --git a/Documentation/merge-strategies.txt 
b/Documentation/merge-strategies.txt
index 1e0728aa12..aa66cbe41e 100644
--- a/Documentation/merge-strategies.txt
+++ b/Documentation/merge-strategies.txt
@@ -23,8 +23,9 @@ recursive::
causing mismerges by tests done on actual merge commits
taken from Linux 2.6 kernel development history.
Additionally this can detect and handle merges involving
-   renames.  This is the default merge strategy when
-   pulling or merging one branch.
+   renames, but currently cannot make use of detected
+   copies.  This is the default merge strategy when pulling
+   or merging one branch.
 +
 The 'recursive' strategy can take the following options:
 
diff --git a/merge-recursive.c b/merge-recursive.c
index 6cc4404144..b618f134d2 100644
--- a/merge-recursive.c
+++ b/merge-recursive.c
@@ -564,6 +564,14 @@ static struct string_list *get_renames(struct 
merge_options *o,
opts.flags.recursive = 1;
opts.flags.rename_empty = 0;
opts.detect_rename = merge_detect_rename(o);
+   /*
+* We do not have logic to handle the detection of copies.  In
+* fact, it may not even make sense to add such logic: would we
+* really want a change to a base file to be propagated through
+* multiple other files by a merge?
+*/
+   if (opts.detect_rename > DIFF_DETECT_RENAME)
+   opts.detect_rename = DIFF_DETECT_RENAME;
opts.rename_limit = o->merge_rename_limit >= 0 ? o->merge_rename_limit :
o->diff_rename_limit >= 0 ? o->diff_rename_limit :
1000;
-- 
2.17.0.294.g8e3b83c0e3

[no subject]

[Scott McKellar]

  Good morning Git

https://bit.ly/2HSZB08



Scott McKellar

[no subject]

[LiN JiNG]

I didn't get any reply from you concerning my last email..

Br
LiN


__

Sky Silk, http://aknet.kz

[no subject]

[Litwiler Diane]

Do you need a convenient direct approved business and personal loan / financing 
with a very low interest rate of 3.00% per annum? We offer urgent loans / 
investment financing. If you are interested, contact the Loan consultant at 
 for more information.

Note: for more information, all responses should be sent to this email address 
.

Thank you.
Management
Copyright © 2018

CONFIDENTIALITY NOTE:  The information contained in this transmission may 
contain privileged and confidential information, including patient information 
protected by federal and state privacy laws. It is intended only for the use of 
the person(s) named above. If you are not the intended recipient, you are 
hereby notified that any review, dissemination, distribution, or duplication of 
this communication is strictly prohibited. Please contact the sender by reply 
email and destroy all copies of the original message. 

Re: [PATCH v5 0/2] *** SUBJECT HERE ***

[Jacob Keller]

On Thu, Apr 5, 2018 at 10:27 PM, Taylor Blau <m...@ttaylorr.com> wrote:
> *** BLURB HERE ***
>

Missing subject and cover letter stuff.. did you submit before you
were ready? or did you not mean to include the cover letter? :)

-Jake

> Taylor Blau (2):
>   builtin/config.c: treat type specifiers singularly
>   builtin/config.c: prefer `--type=bool` over `--bool`, etc.
>
>  Documentation/git-config.txt | 74 +++---
>  builtin/config.c | 77 +++-
>  t/t1300-repo-config.sh   | 29 ++
>  3 files changed, 121 insertions(+), 59 deletions(-)
>
> --
> 2.17.0

[PATCH v5 0/2] *** SUBJECT HERE ***

[Taylor Blau]

*** BLURB HERE ***

Taylor Blau (2):
  builtin/config.c: treat type specifiers singularly
  builtin/config.c: prefer `--type=bool` over `--bool`, etc.

 Documentation/git-config.txt | 74 +++---
 builtin/config.c | 77 +++-
 t/t1300-repo-config.sh   | 29 ++
 3 files changed, 121 insertions(+), 59 deletions(-)

-- 
2.17.0

[no subject]

[Cheah Teng Chye]

发自我的手机

[no subject]

[bbenta]

 hi Git


https://goo.gl/RLDyn8







Bbenta

[no subject]

[Plurality Diversity]

my name is Mrs. Alice Walton, I have a mission for you  which I intend using 
for CHARITY email me: ( i...@alicewonders.us ) for more details

[no subject]

[Roxana Guerrero Nunez]

Herzlichen Glückwunsch, Sie haben € 650.000,00 bei den monatlichen 
Gewinnspielen von Euro Millions / Google Promo am März 2018 gewonnen. 
Kontaktieren Sie unseren Schadenversicherer E-Mail: eurosilli...@gmail.com

1. Vollständiger Name:
2. Adresse:
3. Sex:
4. Alter:
5. Beruf:
6. Telefon:

[no subject]

[Roxana Guerrero Nunez]

Herzlichen Glückwunsch, Sie haben € 650.000,00 bei den monatlichen 
Gewinnspielen von Euro Millions / Google Promo am März 2018 gewonnen. 
Kontaktieren Sie unseren Schadenversicherer E-Mail: eurosilli...@gmail.com

1. Vollständiger Name:
2. Adresse:
3. Sex:
4. Alter:
5. Beruf:
6. Telefon:

[no subject]

[Roxana Guerrero Nunez]

Herzlichen Glückwunsch, Sie haben € 650.000,00 bei den monatlichen 
Gewinnspielen von Euro Millions / Google Promo am März 2018 gewonnen. 
Kontaktieren Sie unseren Schadenversicherer E-Mail: eurosilli...@gmail.com

1. Vollständiger Name:
2. Adresse:
3. Sex:
4. Alter:
5. Beruf:
6. Telefon:

[no subject]

[alfred chow]

Good Day,

I am Mr. Alfred Cheuk Yu Chow, the Director for Credit & Marketing
Chong Hing Bank, Hong Kong, Chong Hing Bank Centre, 24 Des Voeux Road
Central, Hong Kong. I have a business proposal of  $38,980,369.00.

All confirmable documents to back up the claims will be made available
to you prior to your acceptance and as soon as I receive your return
mail.

Email me for more details:

Best Regards,

[no subject]

[Alfred Chow]

Good Day,

  I am sending you this message again.
  I am Mr. Alfred Cheuk Yu Chow, the Director for Credit & Marketing
Chong Hing Bank, Hong Kong, Chong Hing Bank Centre, 24 Des Voeux Road
Central, Hong Kong. I have a business proposal of  $38,980,369.00.

All confirmable documents to back up the claims will be made available
to you prior to your acceptance and as soon as I receive your return
mail.

Email me for more details:

Best Regards.

[no subject]

[Cong ty Tan Van Lang]

Good day, I have business proposition for further reinvestment, if
interested please contact me for details on my emailccb9...@gmail.com

[no subject]

[William Broady]

hihttp://bit.ly/2oxaeuW   William Broady

[no subject]

[Alan Gage]

Hello, I recently noticed a bug involving GitBash and Python. I was
running a function that would post the system time once every second
using a while loop but the text was only sent after the while loop
ended due to a timer I had set. Essesntially, instead of it being
entered every second into the terminal, it was entered all at once,
when the loop ended. I tried this with the Command Line, among other
things, and it worked as intended, with the text being entered every
second. This is on Windows 10 Pro with the Fall Creators Update and
the most recent version of GitBash.

[no subject]

[tboegi]

>From 9f7d43f29eaf6017b7b16261ce91d8ef182cf415 Mon Sep 17 00:00:00 2001
In-Reply-To: <20171218131249.gb4...@sigill.intra.peff.net>
References: <20171218131249.gb4...@sigill.intra.peff.net>
From: =?UTF-8?q?Torsten=20B=C3=B6gershausen?= <tbo...@web.de>
Date: Fri, 23 Feb 2018 20:53:34 +0100
Subject: [PATCH 0/1] Auto diff of UTF-16 files in UTF-8
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Make it possible to show a user-readable diff for UTF-16 encoded files.
This would replace the "binary files differ" with something useful,
without breaking anything for existing users (?).
For future repos the w-t-e encoding can be used, which allows e.g. easier
merging.
People which stick to native UTF-16 because they need the compatiblity
with e.g. libgit2 can still get a readable diff.
Opinions ?

Torsten Bögershausen (1):
  Auto diff of UTF-16 files in UTF-8

 diff.c   | 43 -
 diffcore.h   |  3 ++
 t/t4066-diff-encoding.sh | 98 
 utf8.h   | 11 ++
 4 files changed, 153 insertions(+), 2 deletions(-)
 create mode 100755 t/t4066-diff-encoding.sh

-- 
2.16.1.194.gb2e45c695d

[no subject]

[Alfred Chow]

Good Day,

I am Mr. Alfred Cheuk Yu Chow, the Director for Credit & Marketing Chong
Hing Bank, Hong Kong, Chong Hing Bank Center, 24 Des Voeux Road Central,
Hong Kong. I have a business proposal of $ 38,980,369.00.

All confirmable documents to back up the claims will be made available
to you prior to your acceptance and as soon as I receive your return
mail.

Best Regards.

[no subject]

[Alfred Chow]

Good Day,

I am Mr. Alfred Cheuk Yu Chow, the Director for Credit & Marketing
Chong Hing Bank, Hong Kong, Chong Hing Bank Centre, 24 Des Voeux Road
Central, Hong Kong. I have a business proposal of  $38,980,369.00.

All confirmable documents to back up the claims will be made available
to you prior to your acceptance and as soon as I receive your return
mail.

Email me for more details:

Best Regards.

[no subject]

[Alfred Chow]

Good Day,

I am Mr. Alfred Cheuk Yu Chow, the Director for Credit & Marketing
Chong Hing Bank, Hong Kong, Chong Hing Bank Centre, 24 Des Voeux Road
Central, Hong Kong. I have a business proposal of  $38,980,369.00.

All confirmable documents to back up the claims will be made available
to you prior to your acceptance and as soon as I receive your return
mail.

Email me for more details:

Best Regards.

[no subject]

[Scott McKellar]

 Hi Git

https://goo.gl/q6V2bH


Scott

[no subject]

[Alfred Cheuk Yu Chow]

Good Day,

This is the second time i am sending you this mail.

I am Mr. Alfred Cheuk Yu Chow, the Director for Credit & Marketing Chong
Hing Bank, Hong Kong, need your alliance in a deal that will be of  
mutual benefit.


Email me personally for more details.

Regards.

[no subject]

[Brigadier General Dawn M. Dunlop]

-- 
Dear friend, i am General Brigadier Dawn M Dunlop from U S A, can we
talk?? Very important and urgent please.

[no subject]

[Vanesa Ali]

hola Mi nombre es Vanessa Ali. a France Nationality, soy viuda,
actualmente hospitalizada debido a una enfermedad de cáncer. Mientras
tanto, he decidido donar mi fondo para usted como una persona
confiable que usará este dinero sabiamente, € 2,800,000 Millones de
Euros. para ayudar a los pobres y menos privilegiados. Entonces, si
está dispuesto a aceptar esta oferta y hacer exactamente lo que le
instruiré, vuelva a consultarme para obtener más detalles. Sra.
Vanessa Ali

[no subject]

[Emile Kenold]

-- 
This is Mrs. Emile Kenold a missionary contacting you from London. I
pray you will be kind enough to deliver my £7 million pounds donation
to the less privileged ones in your country and God will bless your
generation for doing this humanitarian work.

I am a widow suffering of lung cancer which has damaged my liver and
back bone and i decided to donate this money to you to use it for
Charity works. Please i want your sincere reply to know if you will be
able to execute this project, and I will give you more information on
how to receive this money. I am waiting for your reply.

Thanks and God bless you.

[no subject]

[mavis lilian wanczyk]

This is the second time i am sending you this mail.

I, Mavis Wanczyk donates $ 5 Million Dollars from part of my Powerball  
Jackpot Lottery of $ 758 Million Dollars, respond with your details  
for claims.


I await your earliest response and God Bless you

Good luck.
Mavis Wanczyk

[no subject]

[imani]

-- 
Hello,

I have a proposal for you.kindly get back to me

Best Regards.
Sherry Brydson

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

[no subject]

[Elizabeth M. Philips]

Belove

My name is Elizabeth M. Philips, i am going on a radical hysterectomy
cervical cancer surgery today. I have WILLED £12,379,000.00 British pounds
to you for the work of the lord. Contact my attorney with my reference number
(NW/XXR/017/053K/PDQ/613X1/UK) for further info. Barr.Luis Jason.
email:luis347ja...@gmail.com

Sincerely Yours,
Mrs.Elizabeth M. Philips.

[no subject]

[Emile Kenold]

I need a good and honest person to claim the sum of seven million
British Pound which i inherited from my late husband. My name is Mrs.
Emile Kenold, presently i am in a very critical health condition in
which I sleep every night without knowing my fate day by day. I am a
widow suffering from long time cancer.

I decided to entrust this fund to a very honest and God fearing person
that will use it for Charity works, orphanages, widows and also build
schools for less privileged ones that will be named after my late
husband if possible.

I took this decision because I do not have any child who will inherit
this money after I die. Please I want your sincere and urgent answer
to know if you will be able to execute this project, and I will give
you more information on how the fund will be transferred to your bank
account. I am waiting for your reply.

[no subject]

[Bobby Smith]

I am contacting you in respect of our late client who deposited fund
valued at the sum of $6,200,000.00 in my bank,he died with his family
in an auto accident. I have contacted you to stand as his heir and
inherit the funds, after the success of this transaction, we should
share the total funds 50%/50% each, reply back if you are interested
 (Bobby sim...@gmail.com)

Best regards,

Mr. Bobby Smith.

[no subject]

[Mario Ernesto Gerala]

You have been awarded a donation of $350,000 USD please reply this email for 
more info : sungla...@gmail.com

[no subject]

[Charles Stanley]

Guess you are fine? I have been trying to reach you! 

[no subject]

[Mario Ernesto Gerala]

You have been awarded a donation of $350,000 USD please reply this email for 
more info : sungla...@gmail.com

[no subject]

[Mark Waite]

subscribe git

Subject for default customers

[jsguerra7]

Dear Sir or Madam,

this is a default email message that gets sent out automatically in the 
licensed version.
This is written in English and will be send out to all people if not some other 
template might match (e.g. the *@*.de one).

As you may see here, you can use different tags like word1 to generate a 
different email each time.

You can also use the following things here:

 git@vger.kernel.org - gets replaced with the email of the person you are 
emailing to
 https://git-scm.com/community - the url where this email was found
 git-scm.com - the domain of the url where the email was found
 N/A - if extra data was collected it will be inserted here


With best Regards
Email Spider
---
Attention! Please never use our software to spam other people.

[no subject]

[Jalus Bilieyich]

[no subject]

[Amir A. K]

-- 
Thanks for your last email response to me.
The information required should include the following-:
Your full names
Your address
Telephone number
Your private email
Occupation
Age
This is to enable my further discussion with you in confidence.
Best regards and wishes to you.
Mohammad Amir Khadov
NB: Please reply to:

am...@postaxte.com

am...@pobox.sk

[no subject]

[Bank Director]

[no subject]

[Director Bank]

Наш офисный контакт, 2554 Дороги Кпэлайм Фэйс Фармаки Бет, Ломе, Залив.

Международный валютный фонд (МВФ) дает компенсацию всем жертвам
жульничества, и Ваш адрес электронной почты был найден в list.this
Денежном грамме жертвы жульничества, и офис Western Union получил
мандат МВФ передать Вашу компенсацию Вам.


однако, мы завершили, чтобы затронуть Вашу собственную оплату
посредством денежного перевода Western Union, 5,000$ ежедневно, пока
полная сумма 850,000.00$ полностью не передана Вам. мы не можем быть в
состоянии послать оплату с одним только Вашим адресом электронной
почты, таким образом нам нужен Ваш
информация как, туда, где мы будем посылать денежные средства, такой как;

Ваш получать имя-
Страна получает-
Номер телефона
Копия паспорта

С уважением
Г-н Тони Вуд
ДИРЕКТОР ДЕНЕЖНОГО ГРАММА И WESTERN UNION ЛОМЕ-ТОГО.
Телефон, +22890272933

[no subject]

[Friedrich Mayhofer]

This is the second time i am sending you this mail.

I, Friedrich Mayrhofer Donates the sum of $ 1,000,000.00 to You, Email Me  
personally for more details.
 

Regards.
Friedrich Mayrhofer

[no subject]

[@United Nation]

The United Nations, World Bank-Group and International Monetary Fund have 
agreed to compensate you with the sum of One Million Five Hundred Thousand US 
Dollars contact us for cliams

[no subject]

[HEARTLAND LOAN FIRM]

Welcome to HEARTLAND LOAN FIRM, we give out loans from the range of € 9,000 to 
€ 900,000,000
at 2% interest rate.

Kindly apply by providing the details below -

Your name ..
Your country ...
Amount of loan needed .
Phone number ...

REGARDS
CHARLENE TAYLOR
HEARTLAND LOAN FIRM 
HEAD OFFICE --52, South Campbell Springfield UNITED KINGDOM
Email: heartlandloancenter8...@gmail.com

[no subject]

[K. Kwan]

hi Git



http://bit.ly/2z5P5es



Yours Truly

K. Kwan

[no subject]

[Lindsey]

Hey,i am Lindsey ,How's everything with you,I have interest on you
after going through your profile I really want to have a good
friendship with you

[no subject]

[Viet Nguyen]

unsubscribe git

[no subject]

[cwestin]

sup Git



http://bit.ly/2zz7jZe



Yours Truly

Cwestin

[no subject]

[hsed]

subscribe git

[no subject]

[hsed]

subscribe git

Subject: Compensation Unit file: IPOH

[Mr.Antonio Guterres]

Subject: Compensation Unit file: IPOH

United Nations Compensation Unit,  In Affiliation with World Bank Our Ref:
Ref: IPOH: ADO/OSHA/33/UN/OSHA/ADO/6410/10/2017



Congratulations Beneficiary,



We have been working closely with the INTERPOL, CIA, FBI and other foreign
international organizations as well as Western Union and Money Gram
regarding all payments you have made in the past and we have the complete
lists and amount you have made so far. However, until this moment you have
failed to receive your payment. We must get you informed that the previous
official you have dealt with have been apprehended and would soon be charged
to court and brought to justice.


We have been having a meeting for quit sometime now and we just came to a
logical conclusion 72 hours ago in affiliation with the World Bank
president. Your email was listed among those that are yet to receive their
compensation payment. The United Nations in Affiliation with World Bank have
agreed to compensate them with the sum of USD7,000, 000.00 (Seven Million
United States Dollars) only.


For this reason, you are to receive your payment through a certified ATM
MASTER CARD. Note, with this Master Card you can withdraw money from any
part of the World without being disturbed or delay and please for no reason
should you disclose your account information as your account information is
not and can never be needed before you receive your card payment. All that
is required of your now is to contact our 100% trust officials by the Name
of Mr.Jimmy Oliver. Below is her contact information:


Name: Mr.Jimmy Oliver
Email: zen...@nmk.ugu.pl



We write to get you informed that everyone has been receiving their card
payments and until this moment you have refuses to receives yours. Below is
the tracking number of beneficiaries that have received their payment in
this month without any problems.
Beneficiary ( Eric Fail Tracking number: 4174072442 Country: U.S.A Website:
www.dhl.com)

And

Beneficiary: (Mohammed Al Aswad Tracking number: 4174074262 Country: Bahrain
Website: www.dhl.com)


Please ensure that you follow the directives and instructions of Mrs. Hana
Moshe so that within 72 hours you would have received your card payment and
your secret pin code issued directly to you for security reasons. We
apologize on behalf of the United Nation Organization for any delay you
might have encountered in receiving your fund in the past. Congratulations,
and I look forward to hear from you as soon as you confirm your payment
making the world a better place.


Yours Faithfully,


General Mr.Antonio Guterres 
Under-Secretary-General for Economic and Social Affairs

Subject: Compensation Unit file: IPOH

[Mr.Antonio Guterres]

Subject: Compensation Unit file: IPOH

United Nations Compensation Unit,  In Affiliation with World Bank Our Ref:
Ref: IPOH: ADO/OSHA/33/UN/OSHA/ADO/6410/10/2017



Congratulations Beneficiary,



We have been working closely with the INTERPOL, CIA, FBI and other foreign
international organizations as well as Western Union and Money Gram
regarding all payments you have made in the past and we have the complete
lists and amount you have made so far. However, until this moment you have
failed to receive your payment. We must get you informed that the previous
official you have dealt with have been apprehended and would soon be charged
to court and brought to justice.


We have been having a meeting for quit sometime now and we just came to a
logical conclusion 72 hours ago in affiliation with the World Bank
president. Your email was listed among those that are yet to receive their
compensation payment. The United Nations in Affiliation with World Bank have
agreed to compensate them with the sum of USD7,000, 000.00 (Seven Million
United States Dollars) only.


For this reason, you are to receive your payment through a certified ATM
MASTER CARD. Note, with this Master Card you can withdraw money from any
part of the World without being disturbed or delay and please for no reason
should you disclose your account information as your account information is
not and can never be needed before you receive your card payment. All that
is required of your now is to contact our 100% trust officials by the Name
of Mr.Jimmy Oliver. Below is her contact information:


Name: Mr.Jimmy Oliver
Email: zen...@nmk.ugu.pl



We write to get you informed that everyone has been receiving their card
payments and until this moment you have refuses to receives yours. Below is
the tracking number of beneficiaries that have received their payment in
this month without any problems.
Beneficiary ( Eric Fail Tracking number: 4174072442 Country: U.S.A Website:
www.dhl.com)

And

Beneficiary: (Mohammed Al Aswad Tracking number: 4174074262 Country: Bahrain
Website: www.dhl.com)


Please ensure that you follow the directives and instructions of Mrs. Hana
Moshe so that within 72 hours you would have received your card payment and
your secret pin code issued directly to you for security reasons. We
apologize on behalf of the United Nation Organization for any delay you
might have encountered in receiving your fund in the past. Congratulations,
and I look forward to hear from you as soon as you confirm your payment
making the world a better place.


Yours Faithfully,


General Mr.Antonio Guterres 
Under-Secretary-General for Economic and Social Affairs

Re: [PATCH v4] doc/SubmittingPatches: correct subject guidance

[Josh Triplett]

On Fri, Nov 10, 2017 at 03:02:50PM +, Adam Dinwoodie wrote:
> The examples and common practice for adding markers such as "RFC" or
> "v2" to the subject of patch emails is to have them within the same
> brackets as the "PATCH" text, not after the closing bracket.  Further,
> the practice of `git format-patch` and the like, as well as what appears
> to be the more common pratice on the mailing list, is to use "[RFC
> PATCH]", not "[PATCH/RFC]".
> 
> Update the SubmittingPatches article to match and to reference the
> `format-patch` helper arguments, and also make some minor text
> clarifications in the area.
> 
> Signed-off-by: Adam Dinwoodie <a...@dinwoodie.org>
> Helped-by: Eric Sunshine <sunsh...@sunshineco.com>

This looks great! Thank you for updating this documentation.

Reviewed-by: Josh Triplett <j...@joshtriplett.org>

> ---
> 
> Notes:
> Changes since v3:
> - Clarified meaning of "RFC" per Eric's suggestion
> - Made the impact of --subject-prefix and friends clearer per Eric's
>   suggestion
> 
> Thank you for your nitpicking, Eric, it's useful and very much
> appreciated :)
> 
>  Documentation/SubmittingPatches | 19 ---
>  1 file changed, 12 insertions(+), 7 deletions(-)
> 
> diff --git a/Documentation/SubmittingPatches b/Documentation/SubmittingPatches
> index 558d465b6..89f239071 100644
> --- a/Documentation/SubmittingPatches
> +++ b/Documentation/SubmittingPatches
> @@ -184,21 +184,26 @@ lose tabs that way if you are not careful.
>  
>  It is a common convention to prefix your subject line with
>  [PATCH].  This lets people easily distinguish patches from other
> -e-mail discussions.  Use of additional markers after PATCH and
> -the closing bracket to mark the nature of the patch is also
> -encouraged.  E.g. [PATCH/RFC] is often used when the patch is
> -not ready to be applied but it is for discussion, [PATCH v2],
> -[PATCH v3] etc. are often seen when you are sending an update to
> -what you have previously sent.
> +e-mail discussions.  Use of markers in addition to PATCH within
> +the brackets to describe the nature of the patch is also
> +encouraged.  E.g. [RFC PATCH] (where RFC stands for "request for
> +comments") is often used to indicate a patch needs further
> +discussion before being accepted, [PATCH v2], [PATCH v3] etc.
> +are often seen when you are sending an update to what you have
> +previously sent.
>  
> -"git format-patch" command follows the best current practice to
> +The "git format-patch" command follows the best current practice to
>  format the body of an e-mail message.  At the beginning of the
>  patch should come your commit message, ending with the
>  Signed-off-by: lines, and a line that consists of three dashes,
>  followed by the diffstat information and the patch itself.  If
>  you are forwarding a patch from somebody else, optionally, at
>  the beginning of the e-mail message just before the commit
>  message starts, you can put a "From: " line to name that person.
> +To change the default "[PATCH]" in the subject to "[]", use
> +`git format-patch --subject-prefix=`.  As a shortcut, you
> +can use `--rfc` instead of `--subject-prefix="RFC PATCH"`, or
> +`-v ` instead of `--subject-prefix="PATCH v"`.
>  
>  You often want to add additional explanation about the patch,
>  other than the commit message itself.  Place such "cover letter"
> -- 
> 2.14.3
> 

[PATCH v4] doc/SubmittingPatches: correct subject guidance

[Adam Dinwoodie]

The examples and common practice for adding markers such as "RFC" or
"v2" to the subject of patch emails is to have them within the same
brackets as the "PATCH" text, not after the closing bracket.  Further,
the practice of `git format-patch` and the like, as well as what appears
to be the more common pratice on the mailing list, is to use "[RFC
PATCH]", not "[PATCH/RFC]".

Update the SubmittingPatches article to match and to reference the
`format-patch` helper arguments, and also make some minor text
clarifications in the area.

Signed-off-by: Adam Dinwoodie <a...@dinwoodie.org>
Helped-by: Eric Sunshine <sunsh...@sunshineco.com>
---

Notes:
Changes since v3:
- Clarified meaning of "RFC" per Eric's suggestion
- Made the impact of --subject-prefix and friends clearer per Eric's
  suggestion

Thank you for your nitpicking, Eric, it's useful and very much
appreciated :)

 Documentation/SubmittingPatches | 19 ---
 1 file changed, 12 insertions(+), 7 deletions(-)

diff --git a/Documentation/SubmittingPatches b/Documentation/SubmittingPatches
index 558d465b6..89f239071 100644
--- a/Documentation/SubmittingPatches
+++ b/Documentation/SubmittingPatches
@@ -184,21 +184,26 @@ lose tabs that way if you are not careful.
 
 It is a common convention to prefix your subject line with
 [PATCH].  This lets people easily distinguish patches from other
-e-mail discussions.  Use of additional markers after PATCH and
-the closing bracket to mark the nature of the patch is also
-encouraged.  E.g. [PATCH/RFC] is often used when the patch is
-not ready to be applied but it is for discussion, [PATCH v2],
-[PATCH v3] etc. are often seen when you are sending an update to
-what you have previously sent.
+e-mail discussions.  Use of markers in addition to PATCH within
+the brackets to describe the nature of the patch is also
+encouraged.  E.g. [RFC PATCH] (where RFC stands for "request for
+comments") is often used to indicate a patch needs further
+discussion before being accepted, [PATCH v2], [PATCH v3] etc.
+are often seen when you are sending an update to what you have
+previously sent.
 
-"git format-patch" command follows the best current practice to
+The "git format-patch" command follows the best current practice to
 format the body of an e-mail message.  At the beginning of the
 patch should come your commit message, ending with the
 Signed-off-by: lines, and a line that consists of three dashes,
 followed by the diffstat information and the patch itself.  If
 you are forwarding a patch from somebody else, optionally, at
 the beginning of the e-mail message just before the commit
 message starts, you can put a "From: " line to name that person.
+To change the default "[PATCH]" in the subject to "[]", use
+`git format-patch --subject-prefix=`.  As a shortcut, you
+can use `--rfc` instead of `--subject-prefix="RFC PATCH"`, or
+`-v ` instead of `--subject-prefix="PATCH v"`.
 
 You often want to add additional explanation about the patch,
 other than the commit message itself.  Place such "cover letter"
-- 
2.14.3

Re: [PATCH v3] doc/SubmittingPatches: correct subject guidance

[Eric Sunshine]

On Thu, Nov 9, 2017 at 8:08 AM, Adam Dinwoodie <a...@dinwoodie.org> wrote:
> The examples and common practice for adding markers such as "RFC" or
> "v2" to the subject of patch emails is to have them within the same
> brackets as the "PATCH" text, not after the closing bracket.  Further,
> the practice of `git format-patch` and the like, as well as what appears
> to be the more common pratice on the mailing list, is to use "[RFC
> PATCH]", not "[PATCH/RFC]".
>
> Update the SubmittingPatches article to match, and to reference the
> `format-patch` helper arguments.
>
> Signed-off-by: Adam Dinwoodie <a...@dinwoodie.org>
> ---
> diff --git a/Documentation/SubmittingPatches b/Documentation/SubmittingPatches
> @@ -184,21 +184,25 @@ lose tabs that way if you are not careful.
>  It is a common convention to prefix your subject line with
>  [PATCH].  This lets people easily distinguish patches from other
> -e-mail discussions.  Use of additional markers after PATCH and
> -the closing bracket to mark the nature of the patch is also
> -encouraged.  E.g. [PATCH/RFC] is often used when the patch is
> +e-mail discussions.  Use of markers in addition to PATCH within
> +the brackets to describe the nature of the patch is also
> +encouraged.  E.g. [RFC PATCH] is often used when the patch is
>  not ready to be applied but it is for discussion, [PATCH v2],

Not a new problem, but since you're here cleaning this up, the "not
ready to be applied but it is for discussion" makes for a clunky read.
Perhaps something roughly like:

E.g. [RFC PATCH] is often used to indicate that a patch needs
further discussion ("request for comments") before being
accepted.

>  [PATCH v3] etc. are often seen when you are sending an update to
>  what you have previously sent.
>
> -"git format-patch" command follows the best current practice to
> +The "git format-patch" command follows the best current practice to
>  format the body of an e-mail message.  At the beginning of the
>  patch should come your commit message, ending with the
>  Signed-off-by: lines, and a line that consists of three dashes,
>  followed by the diffstat information and the patch itself.  If
>  you are forwarding a patch from somebody else, optionally, at
>  the beginning of the e-mail message just before the commit
>  message starts, you can put a "From: " line to name that person.
> +To change the bracketed text at the start of the subject, use
> +`git format-patch --subject-prefix=`.  As a shortcut, you

This may be nit-picky, but it took a bit of thought for me to work out
what "bracketed text at the start of the subject" meant. I wonder if
it would be clearer just to spell it out:

To change the default "[PATCH]" in the subject to "[]", use
`git format-patch --subject-prefix=`.

> +can use `--rfc` instead of `--subject-prefix="RFC PATCH"`, or
> +`-v ` instead of `--subject-prefix="PATCH v"`.

Overall, this is much easier to digest than the run-on sentence in v2. Thanks.

[PATCH v3] doc/SubmittingPatches: correct subject guidance

[Adam Dinwoodie]

The examples and common practice for adding markers such as "RFC" or
"v2" to the subject of patch emails is to have them within the same
brackets as the "PATCH" text, not after the closing bracket.  Further,
the practice of `git format-patch` and the like, as well as what appears
to be the more common pratice on the mailing list, is to use "[RFC
PATCH]", not "[PATCH/RFC]".

Update the SubmittingPatches article to match, and to reference the
`format-patch` helper arguments.

Signed-off-by: Adam Dinwoodie <a...@dinwoodie.org>
Helped-by: Eric Sunshine <sunsh...@sunshineco.com>
---
 Documentation/SubmittingPatches | 12 
 1 file changed, 8 insertions(+), 4 deletions(-)

diff --git a/Documentation/SubmittingPatches b/Documentation/SubmittingPatches
index 558d465b6..ae59fd9d0 100644
--- a/Documentation/SubmittingPatches
+++ b/Documentation/SubmittingPatches
@@ -184,21 +184,25 @@ lose tabs that way if you are not careful.
 
 It is a common convention to prefix your subject line with
 [PATCH].  This lets people easily distinguish patches from other
-e-mail discussions.  Use of additional markers after PATCH and
-the closing bracket to mark the nature of the patch is also
-encouraged.  E.g. [PATCH/RFC] is often used when the patch is
+e-mail discussions.  Use of markers in addition to PATCH within
+the brackets to describe the nature of the patch is also
+encouraged.  E.g. [RFC PATCH] is often used when the patch is
 not ready to be applied but it is for discussion, [PATCH v2],
 [PATCH v3] etc. are often seen when you are sending an update to
 what you have previously sent.
 
-"git format-patch" command follows the best current practice to
+The "git format-patch" command follows the best current practice to
 format the body of an e-mail message.  At the beginning of the
 patch should come your commit message, ending with the
 Signed-off-by: lines, and a line that consists of three dashes,
 followed by the diffstat information and the patch itself.  If
 you are forwarding a patch from somebody else, optionally, at
 the beginning of the e-mail message just before the commit
 message starts, you can put a "From: " line to name that person.
+To change the bracketed text at the start of the subject, use
+`git format-patch --subject-prefix=`.  As a shortcut, you
+can use `--rfc` instead of `--subject-prefix="RFC PATCH"`, or
+`-v ` instead of `--subject-prefix="PATCH v"`.
 
 You often want to add additional explanation about the patch,
 other than the commit message itself.  Place such "cover letter"
-- 
2.14.3

Re: [PATCH v2] doc/SubmittingPatches: correct subject guidance

[Adam Dinwoodie]

On Wednesday 08 November 2017 at 09:10 am -0500, Eric Sunshine wrote:
> On Wed, Nov 8, 2017 at 8:47 AM, Adam Dinwoodie  wrote:
> > +e-mail discussions.  Use of markers in addition to PATCH within
> > +the brackets to describe the nature of the patch is also
> > +encouraged.  E.g. [RFC PATCH] is often used when the patch is not
> > +ready to be applied but it is for discussion, and can be added
> > +with the `--rfc` argument to `git format-patch` or `git
> > +send-email`, while [PATCH v2], [PATCH v3] etc.  are often seen
> 
> It has become a bit of a run-on sentence, but aside from that and the
> unnecessary extra whitespace between "etc." and "are", it looks good
> to me.

Both good points, thank you!  I suspect the extra whitespace was a
result of Vim being "helpful" when reflowing the text.

I'll re-spin now with fixed whitespace and breaking up the sentence a
bit.

Re: [PATCH v2] doc/SubmittingPatches: correct subject guidance

[Eric Sunshine]

On Wed, Nov 8, 2017 at 8:47 AM, Adam Dinwoodie <a...@dinwoodie.org> wrote:
> The examples and common practice for adding markers such as "RFC" or
> "v2" to the subject of patch emails is to have them within the same
> brackets as the "PATCH" text, not after the closing bracket.  Further,
> the practice of `git format-patch` and the like, as well as what appears
> to be the more common pratice on the mailing list, is to use "[RFC
> PATCH]", not "[PATCH/RFC]".
>
> Update the SubmittingPatches article to match.
>
> Signed-off-by: Adam Dinwoodie <a...@dinwoodie.org>
> ---
> diff --git a/Documentation/SubmittingPatches b/Documentation/SubmittingPatches
> @@ -184,12 +184,14 @@ lose tabs that way if you are not careful.
>  It is a common convention to prefix your subject line with
>  [PATCH].  This lets people easily distinguish patches from other
> -e-mail discussions.  Use of additional markers after PATCH and
> -the closing bracket to mark the nature of the patch is also
> -encouraged.  E.g. [PATCH/RFC] is often used when the patch is
> -not ready to be applied but it is for discussion, [PATCH v2],
> -[PATCH v3] etc. are often seen when you are sending an update to
> -what you have previously sent.
> +e-mail discussions.  Use of markers in addition to PATCH within
> +the brackets to describe the nature of the patch is also
> +encouraged.  E.g. [RFC PATCH] is often used when the patch is not
> +ready to be applied but it is for discussion, and can be added
> +with the `--rfc` argument to `git format-patch` or `git
> +send-email`, while [PATCH v2], [PATCH v3] etc.  are often seen

It has become a bit of a run-on sentence, but aside from that and the
unnecessary extra whitespace between "etc." and "are", it looks good
to me.

> +when you are sending an update to what you have previously sent,
> +and can be added with the `-v ` arguments to the same commands.

[PATCH v2] doc/SubmittingPatches: correct subject guidance

[Adam Dinwoodie]

The examples and common practice for adding markers such as "RFC" or
"v2" to the subject of patch emails is to have them within the same
brackets as the "PATCH" text, not after the closing bracket.  Further,
the practice of `git format-patch` and the like, as well as what appears
to be the more common pratice on the mailing list, is to use "[RFC
PATCH]", not "[PATCH/RFC]".

Update the SubmittingPatches article to match.

Signed-off-by: Adam Dinwoodie <a...@dinwoodie.org>
---

I'm re-rolling this patch with some more substantive changes, as a bit
more research points to (a) "RFC PATCH" being more common on this
mailing list than "PATCH/RFC", at least in recent usage, and (b) so the
instructions match the best practice according to `git format-patch` and
friends.

 Documentation/SubmittingPatches | 14 --
 1 file changed, 8 insertions(+), 6 deletions(-)

diff --git a/Documentation/SubmittingPatches b/Documentation/SubmittingPatches
index 558d465b6..95abf6084 100644
--- a/Documentation/SubmittingPatches
+++ b/Documentation/SubmittingPatches
@@ -184,12 +184,14 @@ lose tabs that way if you are not careful.
 
 It is a common convention to prefix your subject line with
 [PATCH].  This lets people easily distinguish patches from other
-e-mail discussions.  Use of additional markers after PATCH and
-the closing bracket to mark the nature of the patch is also
-encouraged.  E.g. [PATCH/RFC] is often used when the patch is
-not ready to be applied but it is for discussion, [PATCH v2],
-[PATCH v3] etc. are often seen when you are sending an update to
-what you have previously sent.
+e-mail discussions.  Use of markers in addition to PATCH within
+the brackets to describe the nature of the patch is also
+encouraged.  E.g. [RFC PATCH] is often used when the patch is not
+ready to be applied but it is for discussion, and can be added
+with the `--rfc` argument to `git format-patch` or `git
+send-email`, while [PATCH v2], [PATCH v3] etc.  are often seen
+when you are sending an update to what you have previously sent,
+and can be added with the `-v ` arguments to the same commands.
 
 "git format-patch" command follows the best current practice to
 format the body of an e-mail message.  At the beginning of the
-- 
2.14.3

[PATCH] doc/SubmittingPatches: correct subject guidance

[Adam Dinwoodie]

The examples and common practice for adding markers such as "RFC" or
"v2" to the subject of patch emails is to have them within the same
brackets as the "PATCH" text.  Update the description to match this
behaviour, rather than asserting such markers should be after the
closing bracket.

Signed-off-by: Adam Dinwoodie <a...@dinwoodie.org>
---
 Documentation/SubmittingPatches | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Documentation/SubmittingPatches b/Documentation/SubmittingPatches
index 558d465b6..e91ce8269 100644
--- a/Documentation/SubmittingPatches
+++ b/Documentation/SubmittingPatches
@@ -184,7 +184,7 @@ lose tabs that way if you are not careful.
 
 It is a common convention to prefix your subject line with
 [PATCH].  This lets people easily distinguish patches from other
-e-mail discussions.  Use of additional markers after PATCH and
+e-mail discussions.  Use of additional markers between PATCH and
 the closing bracket to mark the nature of the patch is also
 encouraged.  E.g. [PATCH/RFC] is often used when the patch is
 not ready to be applied but it is for discussion, [PATCH v2],
-- 
2.14.3

[no subject]

[westerunionbankoff...@gmail.com]

[no subject]

[Jean Carlo Machado]

I hope it's right this time. :)

[no subject]

[小川恭史]

unsubscribe *

[no subject]

[Antoine Beaupré]

sorry for the noise here, but the original patch didn't fix the length
in the right place. v2 fixed it in the library properly, but i forgot
to also include the length of the suffix. this should be good to go...

[no subject]

[Financial Pvt Ltd]

We can help you with a genuine loan to meet your needs.Do you need a personal 
or business loan without stress andQuick approval?Do you need an urgent loan 
today? No Credit Checks* LOAN APPROVAL IN 60MINS !!* GUARANTEED SAME DAY 
TRANSFER !!* 100% APPROVAL RATE !!* LOW INTEREST RATE !!RegardsMrs. Hijab 
Mohammed

(no subject)

[Barr. Richard Williams]

--
Hello,

I am writing you this email to solicit your co-operation and 
partnership  in a business that would benefit us immensely.


I would like to name you the beneficiary to my late client's fund who 
died along with his next-of-kin during a summer vacation in the Middle 
East.


I shall offer you 50 percent of the fund, and you will be in custody of 
my intended  investment in your country with my share.


Do reply for details.

Regards
Richard Williams
Email:richawill1...@gmail.com

[no subject]

[Ella Golan]

I am Ms.Ella Golan, I am the Executive Vice President Banking Division with
FIRST INTERNATIONAL BANK OF ISRAEL LTD (FIBI).
I am getting in touch with you regarding an extremely important and urgent
matter. If you would oblige me the opportunity, I shall provide you with
details upon your Response...

Faithfully,
Ms.Ella Golan

Re: Bug or feature: format-patch breaks long subject lines

[Junio C Hamano]

 writes:

> Is this the expected behaviour?

Yes, it is expected.  Your are seeing the header folding in play.
"mailinfo" (hence "am") will grok it just fine, I think.

Bug or feature: format-patch breaks long subject lines

[stefan.naewe]

Hello list,

git format-patch breaks (or better: word-wraps) long subject lines.

This is on Windows 7 with

$ git --version
git version 2.14.2.windows.2

Reproduce with (some output omitted):

--
$ git init test-format-patch
$ cd test-format-patch
$ touch file
$ git add file
$ git commit 
-m"0123456789012345678901234567890123456789012345678901234567890123456789"
$ git format-patch -1 --stdout
From ec711cca330f1032d286114932a90488542f1da2 Mon Sep 17 00:00:00 2001
From: Stefan Naewe <stefan.na...@gmail.com>
Date: Thu, 12 Oct 2017 10:36:52 +0200
Subject: [PATCH]
 0123456789012345678901234567890123456789012345678901234567890123456789

---
 file | 0
 1 file changed, 0 insertions(+), 0 deletions(-)
 create mode 100644 file

diff --git a/file b/file
new file mode 100644
index 000..e69de29
--
2.14.2.windows.2
--

Is this the expected behaviour?

Thanks,
  Stefan
-- 

/dev/random says: I Have To Stop Now, My Fingers Are Getting Hoarse!
python -c "print 
'73746566616e2e6e616577654061746c61732d656c656b74726f6e696b2e636f6d'.decode('hex')"
 
GPG Key fingerprint = 2DF5 E01B 09C3 7501 BCA9  9666 829B 49C5 9221 27AF