t included in the command itself. Whereas in the
last command I explicitly typed the nonbreaking space and it does
appear as a visible space. I do not know how to reproduce.
Thanks,
Nick
oh, wait, switching branches didn't vaporize my changes, it auto-committed them.
which is still weird and possibly a bug?
Nick Hunt
nhun...@gmail.com
404-988-1845
On Mon, Mar 19, 2018 at 3:13 PM, Nick Hunt wrote:
> i committed my changes, then ran
> git reset --soft HEAD^
>
i committed my changes, then ran
git reset --soft HEAD^
at this point everything is fine
then i switched branches, and all of my changes vaporized into thin
air. uhhh, is this supposed to happen?
anyway, thank god intellij saves my work for me as i go, so i didn't
have to re-write all my code.
my
Ah, the whitespace that was added to enable the >>> markers to be
added... that makes sense.
Which means the output is correct and some assumptions my code makes
about the format of the Combined Diff are wrong.
Thanks!
Nick
On 8 February 2018 at 11:25, Jeff King wrote:
> On Thu,
v branch so should be
prefixed with '+ '.
I'm also not clear why the line beginning 'project does' has both a -
and ++ prefix.
In every description of the Combined Diff format that I've been able
to find, they only show having '+ ' or ' +' prefixes on the actual
content and '++' on the <<<>>> lines.
Am I missing something here?
Thanks,
Nick
e-bug with a
script to easily reproduce.
On Wed, Dec 6, 2017 at 10:00 AM, Nick Snyder wrote:
>> Can you bisect to see when the feature stopped working as you expect?
>
> I will see if I can do that but might take some time.
>
>> It finds up to which commit each line surviv
On Wed, Dec 6, 2017 at 9:22 AM, Junio C Hamano wrote:
> Nick Snyder writes:
>
>> This can be reproduced on Linux and Mac. This behavior seems to be a bug.
>
> Can you bisect to see when the feature stopped working as you expect?
>
> Unlike a forward blame, whe
This can be reproduced on Linux and Mac. This behavior seems to be a bug.
On Wed, Nov 29, 2017 at 12:06 AM, Nick Snyder wrote:
> I have a repo that reproduces a behavior with `git blame --reverse`
> that surprises me. https://github.com/nicksnyder/git-blame-bug
>
> The readme
misunderstanding --reverse or is this a bug?
Thanks!
Nick
$ git --version
git version 2.15.0
Blame of L465 in Tree.tsx at HEAD (ca0fb5) points to L463 at 199ee7
$ git blame -p -L465,465 Tree.tsx
199ee75d1240ae72cd965f62aceeb301ab64e1bd 463 465 1
filename Tree.tsx
public shouldComponentUpdate
by default
> for everybody. New people can first learn using both forms and then
> after they got comfortable with resolving merges, they can choose to
> flip the default for themselves.
--
Thanks,
~Nick Desaulniers
I'm not sure what the `fuzz 2` part means exactly, but it seems like
`git apply` chokes when fuzzing is needed to properly apply a patch.
http://stackoverflow.com/q/6336440/1027966
--
Thanks,
~Nick Desaulniers
On 8 December 2016 at 14:18, Lars Schneider wrote:
>
>> On 08 Dec 2016, at 15:00, Nick Warr wrote:
>>
>> That looks pretty much like the error we're dealing with, any reason
>> why going back a point version on Git (not git-lfs) would resolve the
>> issue
That looks pretty much like the error we're dealing with, any reason
why going back a point version on Git (not git-lfs) would resolve the
issue however?
On 8 December 2016 at 13:57, Lars Schneider wrote:
>
>> On 08 Dec 2016, at 12:46, Nick Warr wrote:
>>
>> Using Git-
is taking place.
The solution is to back level to Git 2.10.2 and the error disappears.
More than willing to provide any further information,
Nick Warr
On 27/10/15 10:56, Davide Fiorentino wrote:
Why not set alias(es) for that?
That counts as a hand-rolled (i.e. ad-hoc) solution. So not out of the
question, but I'd rather point my colleagues at something tried and
tested, rather than simply re-invent wheels, possibly badly.
I'd be interes
ing which does these kind of
things yet?
Thanks!
Nick
--
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
Hello,
Please send me a price list and quotation for your products we want to import
from your country this is a very large order for long term import and urgent
request.
Thank you in advance for your prompt confirmation.
Regards,
Parker Nick
Equipos de Elevaci n , S.A. de C.V.Av. Texcoco
Hello,
Please send me a price list and quotation for your products we want to import
from your country this is a very large order for long term import and urgent
request.
Thank you in advance for your prompt confirmation.
Regards,
Parker Nick
Equipos de Elevaci n , S.A. de C.V.Av. Texcoco
Hello everyone.
Im struggling for a couple of hours to make git store metadata of the
files using metastore and I use hooks/pre-commit for this. The problem
is that the script is invoked correctly, and modifies the file
"metadata" but the file itself is not added into commit. I tried calling
"git a
On 5 Dec 2013, at 11:52, Junio C Hamano wrote:
> Nick Townsend writes:
>
>> Interplay between paths specified in three ways now tested:
>> * After a : in the tree-ish,
>> * As a pathspec in the command,
>> * By virtue of the current working directory
>>
&
regression test enhancements
made to parse_treeish_arg() in archive.c
Helped-by: Eric Sunshine
Signed-off-by: Nick Townsend
---
t/t5004-archive-corner-cases.sh | 71 +
1 file changed, 71 insertions(+)
diff --git a/t/t5004-archive-corner-cases.sh b/t/t5004-archive
From: Nick Townsend
Date: Sat, 30 Nov 2013 16:54:20 -0800
Subject: [PATCH 2/2] Additional git-archive tests
Interplay between paths specified in three ways now tested:
* After a : in the tree-ish,
* As a pathspec in the command,
* By virtue of the current working directory
Note that these tests
From: Nick Townsend
Date: Mon, 25 Nov 2013 15:31:09 -0800
Subject: [PATCH 1/2] submodule: add_submodule_odb() usability
Although add_submodule_odb() is documented as being
externally usable, it is declared static and also
has incorrect documentation. This commit fixes those
and makes no changes
As per the previous patch request, I’ve delayed the work on git-archive.
However the following two patches (attached as replies) should still
be considered.
Kind Regards
Nick--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kerne
From: Nick Townsend
Subject: Re: [PATCH] submodule recursion in git-archive
Date: 2 December 2013 15:55:36 GMT-8
To: Heiko Voigt
Cc: Junio C Hamano , René Scharfe , Jens
Lehmann , git@vger.kernel.org, Jeff King
On 29 Nov 2013, at 14:38, Heiko Voigt wrote:
> On Wed, Nov 27, 2013 at 11
Begin forwarded message:
> From: Nick Townsend
> Subject: Re: [PATCH] submodule recursion in git-archive
> Date: 2 December 2013 16:00:50 GMT-8
> To: Junio C Hamano
> Cc: René Scharfe , Jens Lehmann ,
> git@vger.kernel.org, Jeff King
>
>
> On 27 Nov 2013, at 1
On 27 Nov 2013, at 11:43, Junio C Hamano wrote:
> Nick Townsend writes:
>
>> On 26 Nov 2013, at 14:18, Junio C Hamano wrote:
>>
>>> Even if the code is run inside a repository with a working tree,
>>> when producing a tarball out of an ancient commit
On 26 Nov 2013, at 07:17, René Scharfe wrote:
> Am 26.11.2013 01:04, schrieb Nick Townsend:
>> My first git patch - so shout out if I’ve got the etiquette wrong! Or
>> of course if I’ve missed something.
>
> Thanks for the patches! Please send only one per message (the se
#x27;t normally
>> associate an option with that name with submodules. Would
>> --recurse-submodules alone suffice?
>
> Jens already commented on this, and I agree that --recursive should
> be dropped from this patch.
I only put —recursive because that is what git-clone has for it’s behaviour wrt
submodules.
If that flag is deprecated then I’m fine with using only —recurse-submodules
Perhaps a deprecation flag or note in the code would help?
Overall I’m impressed by the speed and quality of the responses (and the
codebase!) so am glad to
move this forward. I look forward to your feedback.
Kind Regards
Nick
--
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
On 26 Nov 2013, at 14:38, Heiko Voigt wrote:
> Hi,
>
> I like where this is going.
>
> On Tue, Nov 26, 2013 at 04:17:43PM +0100, René Scharfe wrote:
>> Am 26.11.2013 01:04, schrieb Nick Townsend:
>>> + strbuf_addstr(&dotgit, work_tree);
&g
ed patches should be grouped into their own e-mail
> +thread to help readers find all parts of the series. To that end,
> +send them as replies to either an additional "cover letter" message
> +(see below), the first patch, or the respective preceding patch.
> +
> +If your lo
crept in to existing doc and
declarations. It is required
for the second which actually implements the changes.
All comments gratefully received!
Regards
Nick Townsend
Subject: [PATCH 1/2] submodule: add_submodule_odb() usability
Although add_submodule_odb() is documented as being
externally
On Fri, Feb 8, 2013 at 6:05 PM, Jonathan Nieder wrote:
> Junio C Hamano wrote:
>> Nick Muerdter writes:
>
>>> As of git 1.8.1.1 and above (tested up to 1.8.1.3), if the home
>>> directory can't be accessed, it results in a fatal error. In git 1.8.1
>>>
.config/git/config': Permission denied
warning: unable to access '/root/.gitconfig': Permission denied
9375e99f921f428849f19efe2a2e500b3295d1a7 refs/tags/v0.4.0
Thanks,
Nick
--
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
On 21/07/12 15:42, Martin Langhoff wrote:
> On Sat, Jul 21, 2012 at 3:11 AM, Elia Pinto wrote:
>> Well, many folks use puppet in serverless configuration pushing the
>> manifest from a central git server via cron and applying locally the
>> configuration fetched. In this sense git IS used for depl
hould be shown in
`git status` now.
Kind regards,
Nick Douma
signature.asc
Description: OpenPGP digital signature
that too.
>
> It's a pain to have to type username and password every time I need to
> push to github. (Linux here btw).
If you're specifically looking at GitHub and HTTP auth, take a look at
the hub tool:
https://github.com/defunkt/hub
Kind regards,
Nick Douma
signature.asc
Description: OpenPGP digital signature
individual vservers (which are
basically just fancy chroots) can share libraries, binaries and hence
memory, can't muck each other up, but can upgrade their libs/binaries.
--
Nick Craig-Wood <[EMAIL PROTECTED]> -- http://www.craig-wood.com/nick
-
To unsubscribe from this
38 matches
Mail list logo
