Nike Air Max 1 Leopard UK

In here you can sign-up for account, Nike Air Max 1 Leopard UK to become capable for you personally to pick up cash saving deals and very best purchases on each buy. By getting a member on the web site, you'll be able to enjoy outstanding discount

Reset by checkout?

Hi all, One of the more underrepresented command I use in git use on a regular basis is this "reset by checkout". It's what's currently achieved by this convoluted expression: `git checkout -B ` This is such an useful notion that I can fathom why there isn't a better, first-tier, alternative

Re: Nike Air Max 1 Mens Cheap

Uregelmessig bånd stil også hjelper avlaste presset på du og bedre komfort. Nike Free 5.0 V4 Herre , Kjøpt disse nike helt gratis kjøre sko fordi de så moderne og komfortable. Første gang jeg satte dem på var de skjegg. Jeg vil få mye mer Nike gratis opererer i fre

Nike Air Max 1 Mens Cheap

That is seen from the components used towards the numerous technologies that may be identified inside the sneaker. You might have elements from the shoe for example totally free columns that are capable to provide cushioning within the heel, Nike Air Max 90 Cheap UK

Re: [PATCH alt-v1] Improve function dir.c:trim_trailing_spaces()

On Sat, May 31, 2014 at 3:20 AM, Pasha Bolokhov wrote: > Discard unnecessary 'nr_spaces' variable and improve > the 'if' structure. Switch to pointers instead of integers > > Slightly more rare occurrences of 'text \' with a backslash > in between spaces are handled correctly. Namely, the cod

Re: [PATCH v2] t5538: move http push tests out to t5542

On Sat, May 31, 2014 at 12:36 AM, Jeff King wrote: > From: Nick Alcock > > As 0232852b, but for the push tests instead: this avoids a start_httpd > in the middle of the file, which fails under GIT_TEST_HTTPD=false. > > Note that we have to munge the test in a few ways while > moving it: > > 1.

Re: [PATCH v11 39/41] refs.c: propagate any errno==ENOTDIR from _commit back to the callers

Hi, Ronnie Sahlberg wrote: > For these cases, save the errno value and abort and make sure that the caller > can see errno==ENOTDIR. > > Also start defining specific return codes for _commit, assign -1 as a generic > error and -2 as the error that refers to a name conflict. Callers can (and > sho

[PATCH] sideband.c: Get rid of ANSI sequences for non-terminal shell

Some git tools such as GitExtensions for Windows use environment variable TERM=msys which causes the weird ANSI sequence shown for the messages returned from server-side hooks We add those ANSI sequences to help format sideband data on the user's terminal. However, GitExtensions is not using a term

Re: [PATCH] refs.c: change read_ref_at to use the reflog iterators

On Fri, May 30, 2014 at 3:51 PM, Ronnie Sahlberg wrote: > read_ref_at has its own parsing of the reflog file for no really good reason > so lets change this to use the existing reflog iterators. This removes one > instance where we manually unmarshall the reflog file format. > > Log messages for e

Re: [PATCH] refs.c: change read_ref_at to use the reflog iterators

Ronnie Sahlberg writes: > read_ref_at has its own parsing of the reflog file for no really good reason > so lets change this to use the existing reflog iterators. This removes one > instance where we manually unmarshall the reflog file format. > > Log messages for errors are changed slightly. We

[ANNOUNCE] Git v1.9.4

A maintenance release Git v1.9.4 is now available at the usual places. This is expected to be the final maintenance release for the 1.9 series, merging the remaining fixes that are relevant and are already in 2.0. The tarballs are found at: https://www.kernel.org/pub/software/scm/git/ The f

Re: [PATCH v2 2/2] connect.c: replace signal() with sigaction()

Jeremiah Mahler writes: > From signal(2) man page: > > The behavior of signal() varies across UNIX versions, and has also var‐ > ied historically across different versions of Linux. Avoid its use: > use sigaction(2) instead. I don't think this matters for SIG_DFL or SIG_IGN. Andreas.

Re: [ANNOUNCE] Git v2.0.0

Jeff King wrote: > On Wed, May 28, 2014 at 06:17:25PM -0500, Felipe Contreras wrote: > > > This is the last mail I sent to you, because you ignore them anyway, and > > remove them from the mailing list. > > [...] > > [2], a mail you conveniently removed from the tracked record. > > [...] > > You a

Re: [puzzled and solved] "shortlog" not quite understanding all "log" options

Jeff King writes: > On Fri, May 30, 2014 at 12:28:47PM -0700, Junio C Hamano wrote: > >> Aaaand, it turns out that the answer is in the big comment at >> the beginning of handle_revision_pseudo_opt(). >> >> -- >8 -- >> Subject: shortlog: allow --exclude= to be passed >> >> e7b432c5 (revisi

Re: feature request - implement a "GIT_AUTHOR_EMAIL" equivalent, but processed BEFORE .gitconfig

Jeff King writes: > On Fri, May 30, 2014 at 02:58:47PM -0500, Nathan Neulinger wrote: > >> Not really, since there are lots of servers,... > > But I think anything you could set up in the environment could be set up > in an on-the-fly $HOME. For example, instead of: > > GIT_WEAK_AUTHOR_NAME=$na

Re: [PATCH 1/5] fetch doc: update introductory part for clarity

Marc Branchaud writes: > The docs say that all the fetched refs are written to FETCH_HEAD (perhaps a > more accurate name would have been FETCH_HEADS?). If that's truly the case, > it seems weird to use FETCH_HEAD in log and merge commands. (My FETCH_HEAD > file currently has 1434 lines in it -

Re: [RFC PATCH] git log: support "auto" decorations

Jeff King writes: > I wonder if it would be sane to remove or quote NULs when attaching the > buffer to commit->buffer. That would _break_ signatures, but that is a > good thing. I do not think there is a reason to have NULs in your commit > message unless you are doing something malicious (or us

[PATCH v2 0/2] replace signal() with sigaction()

This is the second revision to the patch set to replace signal(2) with sigaction(2) [1]. As Johannes pointed out [2], replacing signal with sigaction would break MinGW compatibility. The first patch in this series addresses this problem by expanding the faux sigaction function in compat/mingw.c t

[PATCH v2 1/2] compat/mingw.c: expand MinGW support for sigaction

Due to portability issues across UNIX versions sigaction(2) should be used instead of signal(2). >From the signal(2) man page: The behavior of signal() varies across UNIX versions, and has also var‐ ied historically across different versions of Linux. Avoid its use: use sigaction(2) ins

[PATCH v2 2/2] connect.c: replace signal() with sigaction()

>From signal(2) man page: The behavior of signal() varies across UNIX versions, and has also var‐ ied historically across different versions of Linux. Avoid its use: use sigaction(2) instead. Replaced signal() with sigaction() in connect.c Signed-off-by: Jeremiah Mahler --- connect.c

Re: [RFC PATCH] git log: support "auto" decorations

Junio C Hamano writes: > Jeff King writes: > >> Subject: [PATCH] reuse commit->buffer when parsing signatures >> ... >> Signed-off-by: Jeff King > > Hmph, unfortunately this seems to break t7510. And I think without re-reading the patch I know what is wrong. The length of the object and strle

Re: [RFC PATCH] git log: support "auto" decorations

On Fri, May 30, 2014 at 01:44:32PM -0700, Junio C Hamano wrote: > Jeff King writes: > > > Subject: [PATCH] reuse commit->buffer when parsing signatures > > ... > > Signed-off-by: Jeff King > > Hmph, unfortunately this seems to break t7510. Urgh, sorry for not testing more thoroughly. I imagi

Re: [RFC PATCH] git log: support "auto" decorations

Jeff King writes: > Subject: [PATCH] reuse commit->buffer when parsing signatures > ... > Signed-off-by: Jeff King Hmph, unfortunately this seems to break t7510. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordom

Re: Git stash gpg prompting

Jeff King writes: > However, I wonder if it is really ever going to be sane to set > commit.gpgsign and not use something like gpg-agent. > > For example, if you > were to ever "git rebase" a patch series (or even just use "git rebase > -i" to refactor commits), you would be prompted for your pas

Re: Git stash gpg prompting

On Fri, May 30, 2014 at 01:07:16PM -0700, Eddie Monge wrote: > Git stash is prompting for passphrase to try to "sign" the changes > being stashed. > > Reproduce: > Add to global gitconfig with signing key: > ``` > [commit] > gpgsign = true > ``` > Go to a repo, make some changes, and then run `

[PATCH alt-v1] Improve function dir.c:trim_trailing_spaces()

Discard unnecessary 'nr_spaces' variable and improve the 'if' structure. Switch to pointers instead of integers Slightly more rare occurrences of 'text \' with a backslash in between spaces are handled correctly. Namely, the code in 8ba87adad6 does not reset 'last_space' when a backslash is e

Re: [puzzled and solved] "shortlog" not quite understanding all "log" options

On Fri, May 30, 2014 at 12:28:47PM -0700, Junio C Hamano wrote: > Aaaand, it turns out that the answer is in the big comment at > the beginning of handle_revision_pseudo_opt(). > > -- >8 -- > Subject: shortlog: allow --exclude= to be passed > > e7b432c5 (revision: introduce --exclude= to ta

Re: feature request - implement a "GIT_AUTHOR_EMAIL" equivalent, but processed BEFORE .gitconfig

On Fri, May 30, 2014 at 02:58:47PM -0500, Nathan Neulinger wrote: > Yes, the behavior currently is: > > If I can figure out "who", I'll set the EMAIL/attributes based on that. > If not, it'll default to the "don't know" behavior that throws up the > list > > Ideally, I'd prefer the

Git stash gpg prompting

Git stash is prompting for passphrase to try to "sign" the changes being stashed. Reproduce: Add to global gitconfig with signing key: ``` [commit] gpgsign = true ``` Go to a repo, make some changes, and then run `git stash` Expected: stash the changes as normal Actual: git prompts for passphra

Re: feature request - implement a "GIT_AUTHOR_EMAIL" equivalent, but processed BEFORE .gitconfig

On 05/30/2014 02:48 PM, Junio C Hamano wrote: Nathan Neulinger writes: I wouldn't mind having a GIT_EMAIL envvar with the semantics you mean, but can you say more about the use case? What's wrong with the usual EMAIL environment variable? EMAIL actually worked for this case for me, but th

[PATCH] refs.c: change read_ref_at to use the reflog iterators

read_ref_at has its own parsing of the reflog file for no really good reason so lets change this to use the existing reflog iterators. This removes one instance where we manually unmarshall the reflog file format. Log messages for errors are changed slightly. We no longer print the file name for t

Re: feature request - implement a "GIT_AUTHOR_EMAIL" equivalent, but processed BEFORE .gitconfig

Nathan Neulinger writes: >> I wouldn't mind having a GIT_EMAIL envvar with the semantics you mean, >> but can you say more about the use case? What's wrong with the usual >> EMAIL environment variable? > > EMAIL actually worked for this case for me, but there wasn't any > equivalent for author n

[puzzled and solved] "shortlog" not quite understanding all "log" options

This gives the list of all recent commits but not the ones that are only reachable from the notes hierarchy: $ git log --exclude=refs/notes/\* --all --no-merges --since=18.hours | git shortlog and we are supposed to be able to write the same with shortlog itself, i.e. $ git shortlog --exclude=

Re: [PATCH 1/5] fetch doc: update introductory part for clarity

On 14-05-30 01:52 PM, Junio C Hamano wrote: > Marc Branchaud writes: > >> On 14-05-29 06:42 PM, Junio C Hamano wrote: >>> + >>> +The names of refs that are fetched, together with the object names >>> +they point at, are written to `.git/FETCH_HEAD`. This information >>> +is used by a later merge

Re: [PATCH] Fix a bug in compat/bswap.h endianness detection

Thanks; this should have been caught during the review. +# if defined(_BIG_ENDIAN) && !defined(_LITTLE_ENDIAN) +# ... +# elif defined(_BIG_ENDIAN) && !defined(_LITTLE_ENDIAN) +# ... +# else -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@v

Re: [PATCH] Improve function dir.c:trim_trailing_spaces()

Jeff King writes: > On Thu, May 29, 2014 at 02:34:33PM -0700, Pasha Bolokhov wrote: > >> > However, I doubt it makes that much of a difference in practice, so >> > unless it's measurable, I would certainly go with the version that is >> > more readable (and correct, of course). >> >> Sorry,

Re: feature request - implement a "GIT_AUTHOR_EMAIL" equivalent, but processed BEFORE .gitconfig

I wouldn't mind having a GIT_EMAIL envvar with the semantics you mean, but can you say more about the use case? What's wrong with the usual EMAIL environment variable? EMAIL actually worked for this case for me, but there wasn't any equivalent for author name, so the commits all look like "sha

Re: [RFC PATCH] git log: support "auto" decorations

On Fri, May 30, 2014 at 02:34:41PM -0400, Jeff King wrote: > On Fri, May 30, 2014 at 10:35:14AM -0700, Junio C Hamano wrote: > > > > Do you want me to roll it up with a real commit message? > > > > Yes. I think the change is sensible. > > Here it is. [...] By the way, I rather derailed Linus'

Re: [RFC PATCH] git log: support "auto" decorations

On Fri, May 30, 2014 at 10:35:14AM -0700, Junio C Hamano wrote: > > Do you want me to roll it up with a real commit message? > > Yes. I think the change is sensible. Here it is. We may want to make these helper functions available to other callers so they can use the same trick, but I do not kn

Re: [RFC PATCH] t5538: move http push tests out to t5542

On 30 May 2014, Junio C. Hamano said: > Nix writes: > >> (signed off with my work email address for paranoia's sake.) > > As long as your employer is fine with your patch contributed to us, My employer encourages it. > and assuming that the patch was done on your employer's time, it That is ha

Re: [RFC PATCH] t5538: move http push tests out to t5542

On 30 May 2014, Jeff King said: > On Fri, May 30, 2014 at 11:29:10AM +0100, Nix wrote: > >> +test_expect_success 'push from shallow repo via http' ' >> +mv "$HTTPD_DOCUMENT_ROOT_PATH/repo.git" shallow-upstream.git && >> +git clone --bare --no-local full "$HTTPD_DOCUMENT_ROOT_PATH/repo.git"

Re: feature request - implement a "GIT_AUTHOR_EMAIL" equivalent, but processed BEFORE .gitconfig

Hi, Nathan Neulinger wrote: > Right now, there isn't any way to have a systemwide profile script > that tries to determine a better default for the user name/email > values, such as in the case of shared logins. The best I've been > able to do for now is use the 'EMAIL' var. I wouldn't mind havi

feature request - implement a "GIT_AUTHOR_EMAIL" equivalent, but processed BEFORE .gitconfig

Four related feature requests/ideas: 1. equivalent to GIT_*_EMAIL/NAME vars, but processed only if git config doesn't set values Right now, there isn't any way to have a systemwide profile script that tries to determine a better default for the user name/email values, such as in the case of s

Re: [PATCH v11 36/41] refs.c: move the check for valid refname to lock_ref_sha1_basic

Ronnie Sahlberg wrote: > Move the check for check_refname_format from lock_any_ref_for_update > to lock_ref_sha1_basic. At some later stage we will get rid of > lock_any_ref_for_update completely. Do you know if this will cause any functional change? What is the potential impact? Is that impact

Re: [PATCH v11 35/41] refs.c: pack all refs before we start to rename a ref

Ronnie Sahlberg wrote: > We want to do this to make it easier to handle atomic renames in rename_ref > for > the case 'git branch -m foo/bar foo'. In an ideal world, a part of me would rather see "git branch -m" doing something more targeted by only packing the two refs it is working with, and o

Re: [PATCH 2/5] fetch doc: update note on '+' in front of the refspec

Marc Branchaud writes: >> +When the remote branch you want to fetch is known to >> +be rewound and rebased regularly, it is expected that >> +the tip of it will not be descendant of the commit that >> +used to be at its tip the last time you fetched it and >> +stored in your remote-tracking branc

Re: [PATCH 1/5] fetch doc: update introductory part for clarity

Marc Branchaud writes: > On 14-05-29 06:42 PM, Junio C Hamano wrote: >> - "Branches" is a more common way to say "heads" in these days. >> >> - Remote-tracking branches are used a lot more these days and it is >>worth mentioning that it is one of the primary side effects of >>the comma

[PATCH 1/2] contrib/subtree: Store subtree metadata in .gittrees file

- Most of the changes are taken from helmo’s repository from following URL: https://github.com/helmo/git-subtree/blob/master/git-subtree.sh - Add code to create a file named .gittrees which can store information on the subtree that is getting merged to the super-repository. The advantage is ‘subtre

[PATCH 2/2] contrib/subtree: List subcmd and modify push/pull to use .gittrees

- Add subtree list sub-command - git subtree list - Lists the subtrees in current project - Changes taken from helmo’s repository from following URL: https://github.com/helmo/git-subtree/blob/master/git-subtree.sh - Add tests for subtree list and subtree push/pull using .gittrees - Files changed in

Re: [PATCH v11 33/41] refs.c: pass the ref log message to _create/delete/update instead of _commit

Ronnie Sahlberg wrote: > Change the reference transactions so that we pass the reflog message > through to the create/delete/update function instead of the commit message. > This allows for individual messages for each change in a multi ref > transaction. Nice. That reminds me: in the future, do

[PATCH v2] t5538: move http push tests out to t5542

From: Nick Alcock As 0232852b, but for the push tests instead: this avoids a start_httpd in the middle of the file, which fails under GIT_TEST_HTTPD=false. Note that we have to munge the test in a few ways while moving it: 1. We drop the `test -z "$GIT_TEST_HTTPD"` check; this is too sim

Re: [RFC PATCH] git log: support "auto" decorations

Jeff King writes: > On Fri, May 30, 2014 at 09:55:14AM -0700, Junio C Hamano wrote: > > I don't think we need to worry about commit->buffer being mucked with. > It is always either NULL, or points to the original object contents. > Encoded log messages are always placed in a separate buffer (and

Re: [PATCH] check_refname_component: Optimize

On Fri, May 30, 2014 at 11:47:33AM +0200, Michael Haggerty wrote: > > I could guess something like "the writer has a different idea of what a > > valid refname is than we do". But that applies as well to (2), but just > > as "the reader who wrote packed-refs.stat has a different idea than we > > d

Re: [PATCH v11 32/41] refs.c: make delete_ref use a transaction

Ronnie Sahlberg wrote: > Signed-off-by: Ronnie Sahlberg > --- > refs.c | 34 +- > 1 file changed, 13 insertions(+), 21 deletions(-) Reviewed-by: Jonathan Nieder [...] > +++ b/refs.c [...] > @@ -2542,24 +2537,21 @@ static int delete_ref_loose(struct ref_lock *lo

Re: [RFC PATCH] t5538: move http push tests out to t5542

Nix writes: > As 0232852b, but for the push tests instead: this avoids a start_httpd > in the middle of the file, which fails under GIT_TEST_HTTPD=false. > > Signed-off-by: Nick Alcock > --- > On 30 May 2014, Jeff King said: >> diff --git a/t/t5537-fetch-shallow.sh b/t/t5537-fetch-shallow.sh >>

Re: [RFC PATCH] t5538: move http push tests out to t5542

On Fri, May 30, 2014 at 11:29:10AM +0100, Nix wrote: > As 0232852b, but for the push tests instead: this avoids a start_httpd > in the middle of the file, which fails under GIT_TEST_HTTPD=false. > > Signed-off-by: Nick Alcock Thanks, this makes sense. I'm really not sure why we didn't notice th

Re: [RFC PATCH] git log: support "auto" decorations

On Fri, May 30, 2014 at 09:55:14AM -0700, Junio C Hamano wrote: > Jeff King writes: > > > On Thu, May 29, 2014 at 09:54:10PM -0700, Linus Torvalds wrote: > > > >> That said, part of it is just that show-signature is so suboptimal > >> performance-wise, re-parsing the commit buffer for each commi

Re: [RFC PATCH] git log: support "auto" decorations

Jeff King writes: > On Thu, May 29, 2014 at 09:54:10PM -0700, Linus Torvalds wrote: > >> That said, part of it is just that show-signature is so suboptimal >> performance-wise, re-parsing the commit buffer for each commit when >> "show_signature" is set. That's just crazy, we've already parsed th

Re: [PATCH] t5537: re-drop http tests

Jeff King writes: > And a final side note. If you retry the merge by: > > m=1ddb4d7 > git checkout $m^1 > git merge $m^2 > > you can see the resulting conflict is quite tricky to understand > Viewing it with diff3 conflict-style makes it much more obvious. Yes, that was a clear mismerg

MAIL

Hello, My name is Mr. Richard Sun from Hong Kong. I want you to be my partner in a business project. Contact me back via my private e-mail address for more details; richadt...@ymail.com Thank you. Mr. Richard Sun. -- To unsubscribe from this list: send the line "unsubscribe git" in the body o

[PATCH] Fix a bug in compat/bswap.h endianness detection

The changes to make detection of endianness more portable had a bug that breaks on (at least) Solaris x86. The bug appears to be a simple copy/paste typo. It checks for _BIG_ENDIAN and not _LITTLE_ENDIAN for both the case where we would decide the system is big endian and little endian. Instead, th

Re: [PATCH 2/5] fetch doc: update note on '+' in front of the refspec

On 14-05-29 06:42 PM, Junio C Hamano wrote: > While it is not *wrong* per-se to say that pulling a rewound/rebased > branch will lead to an unnecessary merge conflict, that is not what > the leading "+" sign to allow non-fast-forward update of remote-tracking > branch is at all. > > Signed-off-by:

Re: [PATCH 1/5] fetch doc: update introductory part for clarity

On 14-05-29 06:42 PM, Junio C Hamano wrote: > - "Branches" is a more common way to say "heads" in these days. > > - Remote-tracking branches are used a lot more these days and it is >worth mentioning that it is one of the primary side effects of >the command to update them. > > - Avoid

[RFC PATCH] t5538: move http push tests out to t5542

As 0232852b, but for the push tests instead: this avoids a start_httpd in the middle of the file, which fails under GIT_TEST_HTTPD=false. Signed-off-by: Nick Alcock --- On 30 May 2014, Jeff King said: > diff --git a/t/t5537-fetch-shallow.sh b/t/t5537-fetch-shallow.sh > index be951a4..a980574 1007

Re: [PATCH] check_refname_component: Optimize

On 05/30/2014 02:07 AM, Jeff King wrote: > On Fri, May 30, 2014 at 06:43:18AM +0700, Duy Nguyen wrote: > The first time we read packed_refs, check_refname_format() is called in read_packed_refs()->create_ref_entry() as usual. If we find no problem, we store packed_refs stat() info i

Re: git 2.0.0 PROFILE=BUILD check-phase problems with ./t5561-http-backend.sh; GIT_TEST_HTTPD=false problems with t5537-fetch-shallow.sh

On 30 May 2014, Jeff King told this: > On Thu, May 29, 2014 at 11:44:37PM +0100, Nix wrote: > >> I observe test failures with git 2.0.0 which are attributable to the >> change to run network tests by default. I'm lumping them both together >> into one report because I'm lazy and I've blown too muc

Re: [BUG REPORT] Git log pretty date

Jeff, Do you have any idea how does github understand that is a bug and fixes it automatically? (I'm saying this because on Github the date is correct). Cumprimentos, Rodrigo Fernandes On Thu, May 29, 2014 at 8:57 PM, Rodrigo Fernandes wrote: > Jeff, > I have no idea what was the tool. The repo

GIT 1.9.2 is listed on Software Informer

Good day! Software.informer.com would like to inform you that your product GIT 1.9.2 has been reviewed by our editors and your program got "100% Clean Award" http://git.software.informer.com/. We would be grateful if you place our award with a link to our review on your website. On our part, w