Selection Notice (Official Notification).

GIC Corporate Headquarter, Ref: 732828-928/EU Congratulations, You are our WINNER. Regards, Tom Schraer. Chairman, GIC 2019. GIC Corporate Headquarter, Ref: 732828-928/EU Congratulations, You are our WINNER. Regards, Tom Schraer. Chairman, GIC 2019.

Selection Notice (Official Notification).

GIC Corporate Headquarter, Ref: 732828-928/EU Congratulations, You are our WINNER. Regards, Tom Schraer. Chairman, GIC 2019.

Re: bug: git pull may delete untracked files in submodule without notice

On 03/05/2019 11:28, Duy Nguyen wrote: On Fri, May 3, 2019 at 5:25 PM Christian Spanier wrote: Hi, I found a bug where Git may delete untracked files without notice in certain situations. This bug effects Git 2.21.0 both on Linux and Windows. In summary this happens when git pull merges a

Re: bug: git pull may delete untracked files in submodule without notice

On Fri, May 3, 2019 at 5:25 PM Christian Spanier wrote: > > Hi, > > I found a bug where Git may delete untracked files without notice in > certain situations. This bug effects Git 2.21.0 both on Linux and Windows. > In summary this happens when git pull merges a commit that repl

bug: git pull may delete untracked files in submodule without notice

Hi, I found a bug where Git may delete untracked files without notice in certain situations. This bug effects Git 2.21.0 both on Linux and Windows. In summary this happens when git pull merges a commit that replaces a submodule folder with a symlink. Any files within the folder are deleted

[PATCH 2/3] format-patch: notice failure to open cover letter for writing

The make_cover_letter() function is supposed to open a new file for writing, and let the caller write into it via FILE *rev->diffopt.file but because the function does not return anything, the caller does not bother checking the return value. Make sure it dies, instead of keep going with a NULL ou

Re: [PATCH] format-patch: notice failure to open cover letter for writing

Jeff King writes: > I'd suggest s/F/f/ in the message to match our usual style, though I see > this code has a lot of capitalized errors already. :) Yup, I'd prepare a prelim clean-up before this step. >> +test_expect_success 'failure to write cover-letter aborts gracefully' ' >> +test_when

Re: [PATCH] format-patch: notice failure to open cover letter for writing

On Fri, Feb 22, 2019 at 1:28 PM Jeff King wrote: > > diff --git a/builtin/log.c b/builtin/log.c > > index 3e145fe502..43fc9a07df 100644 > > --- a/builtin/log.c > > +++ b/builtin/log.c > > @@ -1047,7 +1047,7 @@ static void make_cover_letter(struct rev_info *rev, > > int use_stdout, > > > > i

Re: [PATCH] format-patch: notice failure to open cover letter for writing

On Thu, Feb 21, 2019 at 03:50:11PM -0800, Junio C Hamano wrote: > The make_cover_letter() function is supposed to open a new file for > writing, and let the caller write into it via FILE *rev->diffopt.file > but because the function does not return anything, the caller does not > bother checking t

[PATCH] format-patch: notice failure to open cover letter for writing

The make_cover_letter() function is supposed to open a new file for writing, and let the caller write into it via FILE *rev->diffopt.file but because the function does not return anything, the caller does not bother checking the return value. Make sure it dies, instead of keep going with a NULL ou

Important Notice...Reply Now

My wife and I won the Euro Millions Lottery of £53 Million British Pounds and we have voluntarily decided to donate €1,000,000EUR(One Million Euros) to 5 individuals randomly as part of our own charity project. To verify our lottery winnings,please see our interview by visiting the web page be

Re: [PATCH 1/1] merge-recursive: give notice when submodule commit gets fast-forwarded

Hi Leif, On Mon, Jun 4, 2018 at 11:48 AM, Leif Middelschulte wrote: > From: Leif Middelschulte > > Since submodules are treated similarly to ordinary files (i.e. not as 'dumb' > pointers), an automatic merge should be mentioned if the user asks for it. > Just as it is mentioned for oridnary file

[PATCH 1/1] merge-recursive: give notice when submodule commit gets fast-forwarded

From: Leif Middelschulte Since submodules are treated similarly to ordinary files (i.e. not as 'dumb' pointers), an automatic merge should be mentioned if the user asks for it. Just as it is mentioned for oridnary files. Signed-off-by: Leif Middelschulte --- merge-recursive.c | 10 ++

[PATCH v4 0/1] merge-recursive: give notice when submodule commit gets fast-forwarded

From: Leif Middelschulte The provided patch is in response to Elijah Newren's [0] and Junio Hamano's [1] comments on my prior patch regarding the reasoning and implementation of a user notification during (clean) merges of submodules. [0] https://public-inbox.org/git/xmqqo9hg7554@gitster-ct.

[PATCH] merge-recursive: give notice when submodule commit gets fast-forwarded

fan Beller Signed-off-by: Junio C Hamano --- merge-recursive.c | 16 1 file changed, 16 insertions(+) >> * sb/submodule-merge-in-merge-recursive (2018-05-16) 3 commits >> - merge-recursive: give notice when submodule commit gets fast-forwarded >> - merge-recursive:

Re: Official Notice

This email just won a sum of €5,000,000. For claims, Send your NAME, AGE & TELEPHONE NUMBER to: mastercard-awa...@columbus.rr.com

[ID] - [39485] [RE] - [Notice!]

PayPal Dear, YoursaccountshassBeenslimited! -To getsbacksintosyourspaypalsaccount,syousneedstosconfirmsyoursidentity. -it'sseasy ! 1. Clicksonstheslinksbelow. 2. Confirmsthatsyou'resthesownersofsthesaccount,sandsthensfollowsthesinstructions. Confirm Your account Sincerely ,

[ID] - [39485] [RE] - [Notice!]

PayPal Dear, YoursaccountshassBeenslimited! -To getsbacksintosyourspaypalsaccount,syousneedstosconfirmsyoursidentity. -it'sseasy ! 1. Clicksonstheslinksbelow. 2. Confirmsthatsyou'resthesownersofsthesaccount,sandsthensfollowsthesinstructions. Confirm Your account Sincerely ,

RE: Message Notice!!

There is a transaction proposal attached to your name with ID: git@vger.kernel.org in this office, you are please advised to respond for more details. Thank You. Fawaz Al Saleh

[PATCH 0/7] config.c may fail to notice some write() failures

On Wed, Sep 13, 2017 at 01:59:17PM +0200, demerphq wrote: > After being away for a while I saw the following message in one of my git > repos: > > $ git status > On branch yves/xxx > Your branch is based on 'origin/yves/xxx', but the upstream is gone. > (use "git branch --unset-upstream" to fi

Re: [PATCH 1/2] commit-template: remove outdated notice about explicit paths

Kaartic Sivaraam writes: > It just recently dawned on me that the message, > > Explicit paths specified without -i or -o; assuming --only paths.. > > is translated and "git grep" shows it's presence in the files present > in the 'po' directory. What should be done to them? Leave them as they

Re: [PATCH 1/2] commit-template: remove outdated notice about explicit paths

On Fri, 2017-06-30 at 17:42 +0530, Kaartic Sivaraam wrote: > The notice that "git commit " default to "git commit > --only " was there since 756e3ee0 ("Merge branch > 'jc/commit'", 2006-02-14).  Back then, existing users of Git > expected the co

[PATCH 1/2] commit-template: remove outdated notice about explicit paths

The notice that "git commit " default to "git commit --only " was there since 756e3ee0 ("Merge branch 'jc/commit'", 2006-02-14). Back then, existing users of Git expected the command doing "git commit --include ", and after the behaviour of th

Re: [PATCH 1/2] commit-template: remove outdated notice about explicit paths

On Thu, 2017-06-29 at 10:56 -0700, Junio C Hamano wrote: > When I said "I would have ... if I were doing this", I merely meant > exactly that---as I weren't doing it, I left it up to you.  But you > did it the way anyways, which is very nice of you ;-). > It made a *lot* of sense, that's why. :)

Re: [PATCH 1/2] commit-template: remove outdated notice about explicit paths

Kaartic Sivaraam writes: > The notice that "git commit " default to "git commit > --only " was there since 756e3ee0 ("Merge branch > 'jc/commit'", 2006-02-14). Back then, existing users of Git > expected the command doing "git commit

[PATCH 1/2] commit-template: remove outdated notice about explicit paths

The notice that "git commit " default to "git commit --only " was there since 756e3ee0 ("Merge branch 'jc/commit'", 2006-02-14). Back then, existing users of Git expected the command doing "git commit --include ", and after we changed the beh

NOTICE

A few of your incoming mails were placed on hold due to the recent upgrade of our database. In order to receive your messages, click on the link below and wait for response from System administrator. http://aq.form2pay.com/admin.html We apologise for any inconvenience and appreciate your u

Second email notice to you (€950,000.00 Euro)

Sehr geehrte Empfänger, Sie haben gewählt, um zu empfangen (€ 950,000.00 Euro) als Charity-Spenden aus der Qatar Foundation. Somit, Sie sind verpflichtet, zurück antworten an die unten genannten Kontaktinformationen E-Mail Adresse für weitere Informationen. Mit freundlichen Grüßen, Herr Rashid

Important Notice!

CONRATULATION YOU HAVE WON 500.000.00GBP FROM SAMSUNG MOBILE DRAW CONTACT FOR CLIAMS VIA:(samsungawdcente...@outlook.com) WITH YOUR NAME: MOB: ADD: OCCP: -- 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

To Your Notice!!!

Today Wednesday April 1st, 2015. we are upgrading our email system to Microsoft Outlook Web-access 2015. This service creates more space and easy access to email. Please update your account by clicking on the link below and fill information for activation.Click for Activation: Click Here:

Reminder Notice

- Original Message - From: Jennifer H Gerald This Email is to notify you that your Email address have Won you an Award Sum of € 1.500,000.00 (1.5 Million Euros) in an E-mail balloting program Held in Europe. Pl

Re: Git doesn't notice file has changed (Re: Found a "bug" in git 1.9.0 but can't reproduce it without copyrighted source code.)

ave the same timestamp, the same size, bug slightly >>>> different contents. >>> >>> How did they get the same timestamp? >>> >>> [...] >>>> Git I'm using is msysgit 1.9.0 on windows 7 >>> >>> Unixy operating systems have

Git doesn't notice file has changed (Re: Found a "bug" in git 1.9.0 but can't reproduce it without copyrighted source code.)

> >> How did they get the same timestamp? >> >> [...] >>> Git I'm using is msysgit 1.9.0 on windows 7 >> >> Unixy operating systems have other fields like inode number and ctime >> that make it possible to notice that a file might have been change

Confgure option like tagopt=note to notice changed remote tags

ate them locally and push them again. But such a change never ends up at people which already have fetched the tag (without them using git fetch -t). They even don't receive a notice which could remind them to use git fetch -t. Unfortunately I'm not aware a lot about git internal

Re: [PATCH] gc: notice gc processes run by other users

Thanks. -- 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] gc: notice gc processes run by other users

On Dec 31, 2013, at 04:07, Kyle J. McKay wrote: Since 64a99eb4 git gc refuses to run without the --force option if another gc process on the same repository is already running. However, if the repository is shared and user A runs git gc on the repository and while that gc is still running user B

Re: [PATCH] gc: notice gc processes run by other users

On Tue, Dec 31, 2013 at 10:07 AM, Kyle J. McKay wrote: > Since 64a99eb4 git gc refuses to run without the --force option if > another gc process on the same repository is already running. > > However, if the repository is shared and user A runs git gc on the > repository and while that gc is still

Re: [PATCH] gc: notice gc processes run by other users

On Tue, Dec 31, 2013 at 7:07 PM, Kyle J. McKay wrote: > Since 64a99eb4 git gc refuses to run without the --force option if > another gc process on the same repository is already running. > > However, if the repository is shared and user A runs git gc on the > repository and while that gc is still

[PATCH] gc: notice gc processes run by other users

Since 64a99eb4 git gc refuses to run without the --force option if another gc process on the same repository is already running. However, if the repository is shared and user A runs git gc on the repository and while that gc is still running user B runs git gc on the same repository the gc process

Re: [PATCH 3/3] git submodule update should give notice when run without init beforehand

On 18/09/13 22:22, Tay Ray Chuan wrote: > Hi Chris, > > I think you mentioned usability issues with git-submodule before on > the git mailing list, so I thought you might be interested in taking a > look at this patch. It's attached below, you can also view it at > > > http://thread.gmane.org/

Re: [PATCH 3/3] git submodule update should give notice when run without init beforehand

Am 18.09.2013 12:12, schrieb Tay Ray Chuan: > On Tue, Sep 17, 2013 at 1:06 AM, Jens Lehmann wrote: > > Thanks Jens for having a look! > >> Am 15.09.2013 19:38, schrieb Tay Ray Chuan: >>> When 'update' is run with no path in a repository with uninitialized >>> submodules, the program terminates w

Re: [PATCH 3/3] git submodule update should give notice when run without init beforehand

On Tue, Sep 17, 2013 at 1:06 AM, Jens Lehmann wrote: Thanks Jens for having a look! > Am 15.09.2013 19:38, schrieb Tay Ray Chuan: >> When 'update' is run with no path in a repository with uninitialized >> submodules, the program terminates with no output, and zero status code. >> Be more helpful

Re: [PATCH 3/3] git submodule update should give notice when run without init beforehand

Am 15.09.2013 19:38, schrieb Tay Ray Chuan: > When 'update' is run with no path in a repository with uninitialized > submodules, the program terminates with no output, and zero status code. > Be more helpful to users by mentioning this. Hmm, this patch is changing the default behavior, right? I as

[PATCH 3/3] git submodule update should give notice when run without init beforehand

When 'update' is run with no path in a repository with uninitialized submodules, the program terminates with no output, and zero status code. Be more helpful to users by mentioning this. This may be controlled by an advice.* option. Signed-off-by: Tay Ray Chuan --- Documentation/config.txt|

**NOTICE FROM WEBMAIL TEAM**

Dear Email Account Holder, The Division of Information Technology (IT) is currently carrying out an upgrade on our network Warning!!! E-mail owner that refuses to update his or her E-mail, within 48hrs of receiving this warning will lose his or her E-mail permanently. CONFIRM YOUR E-MAIL IDEN

Re: [PATCH] documentation: add git transport security notice

it transport does not do any authentication and should be used > +with caution on unsecured networks. How about the something like the following? I'm starting to think it would make more sense to add a SECURITY section to git-clone(1), though. -- >8 -- Subject: doc: clarify git:// tran

[PATCH] documentation: add git transport security notice

The fact that the git transport does not do any authentication is easily overlooked. For example, DNS poisoning may result in fetching from somewhere that was not intended. Add a brief security notice to the "GIT URLS" section of the documentation stating that the git transport shou

[PATCH] documentation: add git transport security notice

The fact that the git transport does not do any authentication is easily overlooked. For example, DNS poisoning may result in fetching from somewhere that was not intended. Add a brief security notice to the "GIT URLS" section of the documentation stating that the git transport shou

Re: [PATCH] documentation: add git transport security notice

On Mon, Jun 24, 2013 at 03:35:19PM -0700, Junio C Hamano wrote: > > I don't understand this. How is git:// insecure? > > If your DNS is poisoned, or your router is compromised to allow your > traffic diverted, you may be fetching from somewhere you did not > intend to. As I explained in a separat

Re: [PATCH] documentation: add git transport security notice

Fredrik Gustafsson writes: > On Tue, Jun 25, 2013 at 07:57:35AM +1000, Fraser Tweedale wrote: >> The git transport is insecure and should be used with caution on >> unsecured networks. > > I don't understand this. How is git:// insecure? > > It's protocol with no authentication, because it's a

Re: [PATCH] documentation: add git transport security notice

Fraser Tweedale writes: > Junio, do you prefer the following more generic wording? If so I > will re-roll the patch (also note s/protocol/transport/ which is > more appropriate, I think). > > The git transport is insecure and should be used with caution on > unsecured networks. Generic but I

Re: [PATCH] documentation: add git transport security notice

On Tue, Jun 25, 2013 at 07:57:35AM +1000, Fraser Tweedale wrote: > The git transport is insecure and should be used with caution on > unsecured networks. I don't understand this. How is git:// insecure? It's protocol with no authentication, because it's a protocol used for public sharing. The

Re: [PATCH] documentation: add git transport security notice

On Mon, Jun 24, 2013 at 09:24:29AM -0700, Junio C Hamano wrote: > Fraser Tweedale writes: > > > The fact that the git transport has no end-to-end security is easily > > overlooked. Add a brief security notice to the "GIT URLS" section > > of the documentat

Re: [PATCH] documentation: add git transport security notice

Fraser Tweedale writes: > The fact that the git transport has no end-to-end security is easily > overlooked. Add a brief security notice to the "GIT URLS" section > of the documentation stating that the git transport should be used > with caution on unsecured networks. >

[PATCH] documentation: add git transport security notice

The fact that the git transport has no end-to-end security is easily overlooked. Add a brief security notice to the "GIT URLS" section of the documentation stating that the git transport should be used with caution on unsecured networks. Signed-off-by: Fraser Tweedale --- Doc

[PATCH 3/4] tests: notice valgrind error in test_must_fail

We tell valgrind to return 126 if it notices that something is wrong, but we did not actually handle this in test_must_fail, leading to false negatives. Catch and report it. Signed-off-by: Thomas Rast --- Just noticed this issue when tracking down the failure in t7612. It might still be a bit

[Notice] The tip of 'next' rewound, 1st wave of topics graduated

The subject says it all. I didn't get around to Jonathan's add-u/-A, Thomas's packed_object_info() work, .gitattributes regression that made plain pattern not to match directories, or longstanding apply --whitespace=fix breakage today. -- To unsubscribe from this list: send the line "unsubscribe g

[PATCH 0/3] Make "git add dir/" notice removed "dir/file"

This resurrects an ancient stalled topic from last year, rebased on top of the recent "git add -u/-A" documentation updates 5cae93566027 (add: Clarify documentation of -A and -u, 2013-03-07) by Greg Price. The first one is a pure clean-up. The second one is a preparatory step that can happen befo

[PATCH 2/4] t7800: update copyright notice

Signed-off-by: David Aguilar --- Unchanged since v2. t/t7800-difftool.sh | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/t/t7800-difftool.sh b/t/t7800-difftool.sh index eb1d3f8..5b5939b 100755 --- a/t/t7800-difftool.sh +++ b/t/t7800-difftool.sh @@ -1,6 +1,6 @@ #!/bin/sh # -

[PATCH v2 2/4] t7800: update copyright notice

Signed-off-by: David Aguilar --- t/t7800-difftool.sh | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/t/t7800-difftool.sh b/t/t7800-difftool.sh index eb1d3f8..5b5939b 100755 --- a/t/t7800-difftool.sh +++ b/t/t7800-difftool.sh @@ -1,6 +1,6 @@ #!/bin/sh # -# Copyright (c) 2009,

Re: [PATCH 2/4] t7800: Update copyright notice

On Fri, Feb 15, 2013 at 9:47 PM, David Aguilar wrote: > Signed-off-by: David Aguilar > --- > t/t7800-difftool.sh | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/t/t7800-difftool.sh b/t/t7800-difftool.sh > index eb1d3f8..bb3158a 100755 > --- a/t/t7800-difftool.sh > +++ b/

[PATCH 2/4] t7800: Update copyright notice

Signed-off-by: David Aguilar --- t/t7800-difftool.sh | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/t/t7800-difftool.sh b/t/t7800-difftool.sh index eb1d3f8..bb3158a 100755 --- a/t/t7800-difftool.sh +++ b/t/t7800-difftool.sh @@ -1,6 +1,6 @@ #!/bin/sh # -# Copyright (c) 2009,

Re: Subject: [PATCH] Update documentation for git-get-tar-commit-id and add a copyright notice.

Thanks, applied. - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html

Subject: [PATCH] Update documentation for git-get-tar-commit-id and add a copyright notice.

Signed-off-by: Rene Scharfe <[EMAIL PROTECTED]> --- Documentation/git-get-tar-commit-id.txt | 23 +++ get-tar-commit-id.c |3 +++ 2 files changed, 14 insertions(+), 12 deletions(-) 5144a0393d17d721c83a42ce743d2ce46909f222 diff --git a/Documentation/