On 6 June 2017 at 00:29, Luke Diamand wrote:
> On 5 June 2017 at 19:50, Андрей Ефанов <1134t...@gmail.com> wrote:
>> 2017-06-04 14:09 GMT+03:00 Luke Diamand :
>>>
>>>
>>> >
>>> > The problem, as I see it, is that before syncing changes in the given
>>> > range, p4 task does not sync to cl1 version
On Mon, Jun 05, 2017 at 05:14:01PM -0400, Hector Santos wrote:
> I'm implementing GIT. If there an option or compile/version that "keep"
> file timestamps?
Just in case you've missed it, there's an explanation of why Git behaves
the way it does in this regard [1].
1.
https://git.wiki.kernel.or
On Tue, Jun 6, 2017 at 2:10 AM, Junio C Hamano wrote:
> Sahil Dua writes:
>
>> I want suggestions about one logical point raised by Evar.
>>
>> Let's consider a case that I'm on branch maint and then I do 'git
>> checkout master' followed by 'git branch -m feature', it will rename
>> master branc
On 6 June 2017 at 08:00, Luke Diamand wrote:
> On 6 June 2017 at 00:29, Luke Diamand wrote:
>> On 5 June 2017 at 19:50, Андрей Ефанов <1134t...@gmail.com> wrote:
>>> 2017-06-04 14:09 GMT+03:00 Luke Diamand :
>
> The problem, as I see it, is that before syncing changes in the g
2017-06-06 10:49 GMT+03:00 Luke Diamand :
> On 6 June 2017 at 08:00, Luke Diamand wrote:
>> On 6 June 2017 at 00:29, Luke Diamand wrote:
>>> On 5 June 2017 at 19:50, Андрей Ефанов <1134t...@gmail.com> wrote:
2017-06-04 14:09 GMT+03:00 Luke Diamand :
>
>
> >
> > The problem, a
Dear Talented,
I am Talent Scout For Sony Pictures Animation, Present Sony Pictures Animation
Movies a Film Corporation Located in the United State, is Soliciting for the
Right to use Your Photo/Face and Personality as One of the Semi -Major
Role/ Character in our Upcoming ANIMATED Stereoscope 3D
On Tue, Jun 6, 2017 at 3:27 AM, Junio C Hamano wrote:
> Sahil Dua writes:
>
>> Adds a test for the case when only one parameter is passed to '-m'
>> (move/rename) option.
>>
>> For example - if 'git branch -m bbb' is run, it should rename the
>> currently checked out branch to bbb. There was no t
On Mon, Jun 5, 2017 at 8:23 PM, Stefan Beller wrote:
>
> > [...]
> > "git diff" has been taught to optionally paint new lines that are
> > the same as deleted lines elsewhere differently from genuinely new
> > lines.
> >
> > Are we happy with these changes?
I've been studiously ignoring this
On Tue, Jun 06, 2017 at 10:20:45AM +0900, Junio C Hamano wrote:
> Ævar Arnfjörð Bjarmason writes:
>
> > That looks scary, can you please comment out this:
> >
> > #define SHA1DC_ALLOW_UNALIGNED_ACCESS
> >
> > In sha1dc/sha1.c and see if that helps, alternatively comment out the
> > ifdefs gua
On Tue, Jun 6, 2017 at 9:39 AM, Ævar Arnfjörð Bjarmason
wrote:
> On Tue, Jun 6, 2017 at 2:10 AM, Junio C Hamano wrote:
>> Sahil Dua writes:
>>
>>> I want suggestions about one logical point raised by Evar.
>>>
>>> Let's consider a case that I'm on branch maint and then I do 'git
>>> checkout mas
On 6 June 2017 at 08:56, Андрей Ефанов <1134t...@gmail.com> wrote:
>>
>> It seems to be something to do with the code around line 3395 that says:
>>
>> if self.changeRange == "@all":
>> self.changeRange = ""
>> elif ',' not in self.changeRange:
>>
>> It's finding a lower revision nu
From: "David"
On 6 June 2017 at 11:52, Junio C Hamano wrote:
Samuel Lijin writes:
For what it's worth, I've never quite understood the "Initial commit"
message, because the repository is in a state where there are no
commits yet, not when HEAD is pointing to a root commit.
In the context
> >> In the context of "status", it probably is more logically correct if
> >> it said "No commit yet" or something. This is no longer "is initial
> >> harder than root?" ;-)
> >
> > Exactly. I agree with OP, in the context of running 'git status', I find
> > the string "Initial commit" confusing
"Philip Oakley" writes:
> From: "David"
>
>> Perhaps say something like "Repository is empty." there.
>
>
> I like that. I think that is a very appropriately descriptive statement.
>
> An alternative ,with slightly less textual change, could be "Waiting
> for initial commit"
>
I can buy that
Adam Dinwoodie writes:
> Digging briefly into the endianness detection, it appears Cygwin has
> both _LITTLE_ENDIAN and _BIG_ENDIAN defined. Git's detection works by
> assuming it's in a little endian environment and switching to big endian
> if it detects any of the defines that indicate such,
Ævar Arnfjörð Bjarmason writes:
> On Tue, Jun 6, 2017 at 2:10 AM, Junio C Hamano wrote:
>
>> When somebody says "I want to rename my current branch to X", it is
>> clear that the person wants to end up being on a branch called X.
>>
>> To me, "I want to copy my current branch to Y" sounds more l
On Tue, Jun 06, 2017 at 08:55:04PM +0900, Junio C Hamano wrote:
> Adam Dinwoodie writes:
>
> > Digging briefly into the endianness detection, it appears Cygwin has
> > both _LITTLE_ENDIAN and _BIG_ENDIAN defined. Git's detection works by
> > assuming it's in a little endian environment and switc
One could have configure ask some existing dependency that has already
determined the byte order. For example:
# perl -e 'use Config; $o=$Config{byteorder}; print(($o=~/^1234/ ?
"little" : ($o=~/4321$/ ? "big" : "weird")), "\n");'
little
Good: less #ifdef soup; bad: not so great for cross-compil
On Mon, Jun 05, 2017 at 11:42:31AM -0700, Stefan Beller wrote:
> So I was wondering if there is a command that shows all trailers?
> Similar to a "shortlog -sne" I would want to have a list of all trailers.
> This is because there might be an even more popular trailer than
> "Helped-by", but we wou
git version 2.6.3
OS: RHEL 6
Work around found in:
https://stackoverflow.com/questions/3040833/stash-only-one-file-out-of-multiple-files-that-have-changed-with-git
Workaround is not very optimal. Please add this support to git.
--
==
Rajdeep
=
-Original Message-
On June 6, 2017 9:23 AM, rajdeep mondal wrote:
>Work around found in:
>https://stackoverflow.com/questions/3040833/stash-only-one-file-out-of-multiple-files-that-have-changed-with-git
>Workaround is not very optimal. Please add this support to git.
Instead of using stash
rajdeep mondal writes:
> git version 2.6.3
> OS: RHEL 6
>
> Work around found in:
> https://stackoverflow.com/questions/3040833/stash-only-one-file-out-of-multiple-files-that-have-changed-with-git
>
> Workaround is not very optimal. Please add this support to git.
This has been implemented in Gi
On Tue, 2017-06-06 at 20:52 +0900, Junio C Hamano wrote:
> "Waiting for the initial commit", or "No commits yet", can be
> explained to describe the state of the current branch (not the state
> of the repository), and it is correct that we do not have any commit
> on the branch, and the branch is w
Do we have Jenkins (or something else) setup for Git?
We would be happy to donate (slave) VMs for cygwin builds og Git.
-Jason Pyeron
> On 06 Jun 2017, at 16:47, Jason Pyeron wrote:
>
> Do we have Jenkins (or something else) setup for Git?
>
> We would be happy to donate (slave) VMs for cygwin builds og Git.
>
> -Jason Pyeron
>
We use TravisCI for Linux, Mac, and (in a special way) Windows:
https://travis-ci.org/git/git
Update sha1dc from the latest version by the upstream
maintainer[1].
See commit a0103914c2 ("sha1dc: update from upstream", 2017-05-20) for
the latest update. That update was done sans some whitespace changes
by upstream, which is why the diff here isn't the same as the upstream
cc46554..e139984.
Add an option to use the sha1collisiondetection library from the
submodule in sha1collisiondetection/ instead of in the copy in the
sha1dc/ directory.
This allows us to try out the submodule in sha1collisiondetection
without breaking the build for anyone who's not expecting them as we
work out any
This updates sha1dc fixing the issue on Cygwin introduced in 2.13.1,
and hopefully not regressing elsewhere. Liam, it would be much
appreciated if you could test this on SPARC.
As before the "sha1dc: update from upstream" patch is what should
fast-track to master/maint and be in 2.13.2, the other
From: Junio C Hamano
If a user wants to experiment with the version of collision
detecting sha1 from the submodule, the user needed to not just
populate the submodule but also needed to turn the knob.
A Makefile trick is easy enough to do so, so let's do this. When
somebody with a copy of the s
On Mon, Jun 05, 2017 at 07:36:58PM -0400, Hector Santos wrote:
> Do you see any technical issues with using programmable hooks or something
> like this would have to be patched in? I am giving it a serious thought to
> exploring a fix to the Git Daemon over the wire completion issues on
> Windows.
Reproduction:
- Start git gui
- Go to menu panel: Help > About Git Gui
Output:
error: git-gui died of signal 11
Environment:
Debian 8 jessie amd64 KDE
--
Regards,
Konstantin Podsvirov
On Mon, Jun 5, 2017 at 8:56 PM, Jeff King wrote:
> While running some regression tests with v2.13, I noticed an odd
> behavior. If I create a repository where there's a gitlink with no
> matching .gitmodules entry:
>
> git init repo
> cd repo
> n10=1234abcdef
> n40=$n10$n10$n10$n10
> git
On 06/06, Stefan Beller wrote:
> On Mon, Jun 5, 2017 at 8:56 PM, Jeff King wrote:
> > While running some regression tests with v2.13, I noticed an odd
> > behavior. If I create a repository where there's a gitlink with no
> > matching .gitmodules entry:
> >
> > git init repo
> > cd repo
> >
On Mon, Jun 5, 2017 at 10:18 AM, Jeff King wrote:
> Yeah, I agree it is safe now. I'm just worried about some function in
> remote.c later doing:
>
>read_config();
>add_and_parse_fetch_refspec(remotes[0], whatever);
>
> which leaves the struct in an inconsistent state (we realloc NULL whic
On Tue, Jun 6, 2017 at 8:12 AM, Ævar Arnfjörð Bjarmason
wrote:
> This updates sha1dc fixing the issue on Cygwin introduced in 2.13.1,
> and hopefully not regressing elsewhere. Liam, it would be much
> appreciated if you could test this on SPARC.
>
> As before the "sha1dc: update from upstream" pat
On Tue, Jun 6, 2017 at 10:34 AM, Konstantin Podsvirov
wrote:
> Reproduction:
> - Start git gui
> - Go to menu panel: Help > About Git Gui
>
> Output:
> error: git-gui died of signal 11
>
> Environment:
> Debian 8 jessie amd64 KDE
Care to also share the output of
$ git gui --version
$ git --v
On Tue, Jun 06, 2017 at 08:19:09PM +0200, SZEDER Gábor wrote:
> > if (!remote->fetch)
> > BUG("cannot add refspec to an unparsed remote");
> >
> > ?
>
> But as mentioned before, remote->fetch being NULL is not a bug in
> itself, it's a perfectly valid value even in a fully parsed remote
Hi Randall,
I completely agree to what you are saying, but sometimes it just so
happens that in the middle of a change, i feel like if some portion of
the changes are fine I can commit them. Stashing some of the files
and being able to check the compile/tests at this point would be a
really aweso
On Tue, Jun 06, 2017 at 11:10:24AM -0700, Brandon Williams wrote:
> > > This bisects to your bb62e0a99 (clone: teach --recurse-submodules to
> > > optionally take a pathspec, 2017-03-17). That patch just sets
> > > submodule.active by default, so I think the real issue is probably in
> > > a086f92
On Tue, Jun 06, 2017 at 01:43:55PM +0200, SZEDER Gábor wrote:
> > An alternative ,with slightly less textual change, could be "Waiting for
> > initial commit"
> >
>
> We should consider orphan/unborn branches, too:
>
> git (master)$ git checkout --orphan newroot
> Switched to a new branch
On Tue, Jun 6, 2017 at 8:12 AM, Ævar Arnfjörð Bjarmason
wrote:
> Add an option to use the sha1collisiondetection library from the
> submodule in sha1collisiondetection/ instead of in the copy in the
> sha1dc/ directory.
>
> This allows us to try out the submodule in sha1collisiondetection
> withou
On Tue, Jun 6, 2017 at 8:23 PM, Stefan Beller wrote:
> On Tue, Jun 6, 2017 at 8:12 AM, Ævar Arnfjörð Bjarmason
> wrote:
>> This updates sha1dc fixing the issue on Cygwin introduced in 2.13.1,
>> and hopefully not regressing elsewhere. Liam, it would be much
>> appreciated if you could test this o
On Tue, Jun 06, 2017 at 02:42:01PM -0400, Jeff King wrote:
> > "Waiting for initial commit" is much better even in this case, but I
> > still don't like that "initial", though I can't say why, and don't
> > have any better suggestion either. Though users experienced enough to
> > create an empty
On Tue, Jun 06, 2017 at 08:51:35PM +0200, Ævar Arnfjörð Bjarmason wrote:
> On Tue, Jun 6, 2017 at 8:23 PM, Stefan Beller wrote:
> > On Tue, Jun 6, 2017 at 8:12 AM, Ævar Arnfjörð Bjarmason
> > wrote:
> >> This updates sha1dc fixing the issue on Cygwin introduced in 2.13.1,
> >> and hopefully not
On Tue, Jun 6, 2017 at 8:48 PM, Stefan Beller wrote:
> On Tue, Jun 6, 2017 at 8:12 AM, Ævar Arnfjörð Bjarmason
> wrote:
>> Add an option to use the sha1collisiondetection library from the
>> submodule in sha1collisiondetection/ instead of in the copy in the
>> sha1dc/ directory.
>>
>> This allows
On Tue, Jun 6, 2017 at 9:01 PM, Jeff King wrote:
> On Tue, Jun 06, 2017 at 08:51:35PM +0200, Ævar Arnfjörð Bjarmason wrote:
>
>> On Tue, Jun 6, 2017 at 8:23 PM, Stefan Beller wrote:
>> > On Tue, Jun 6, 2017 at 8:12 AM, Ævar Arnfjörð Bjarmason
>> > wrote:
>> >> This updates sha1dc fixing the issu
> Subject: sha1dc: ignore indent-with-non-tab whitespace violations
>
> The upstream sha1dc code indents some lines with spaces.
> While this doesn't match Git's coding guidelines, it's better
> to leave this imported code untouched than to try to make it
> match our style. However, we can use .git
On Tue, Jun 6, 2017 at 12:03 PM, Ævar Arnfjörð Bjarmason
wrote:
> On Tue, Jun 6, 2017 at 8:48 PM, Stefan Beller wrote:
>> On Tue, Jun 6, 2017 at 8:12 AM, Ævar Arnfjörð Bjarmason
>> wrote:
>>> Add an option to use the sha1collisiondetection library from the
>>> submodule in sha1collisiondetection
06.06.2017, 21:25, "Stefan Beller" :
> On Tue, Jun 6, 2017 at 10:34 AM, Konstantin Podsvirov
> wrote:
>> Reproduction:
>> - Start git gui
>> - Go to menu panel: Help > About Git Gui
>>
>> Output:
>> error: git-gui died of signal 11
>>
>> Environment:
>> Debian 8 jessie amd64 KDE
>
> Care to
> On 05 Jun 2017, at 21:15, Jeff King wrote:
>
> Commit a1283866b (t5313: test bounds-checks of
> corrupted/malicious pack/idx files, 2016-02-25) added a test
> that requires our corrupted pack index to have two objects.
> The entry for the first one remains untouched, but we
> corrupt the entry
On Tue, Jun 06, 2017 at 02:38:08PM -0400, rajdeep mondal wrote:
> Hi Randall,
>
> I completely agree to what you are saying, but sometimes it just so
> happens that in the middle of a change, i feel like if some portion of
> the changes are fine I can commit them. Stashing some of the files
> and
Thanks Mike.
On Tue, Jun 6, 2017 at 5:03 PM, Mike Hommey wrote:
> On Tue, Jun 06, 2017 at 02:38:08PM -0400, rajdeep mondal wrote:
>> Hi Randall,
>>
>> I completely agree to what you are saying, but sometimes it just so
>> happens that in the middle of a change, i feel like if some portion of
>> t
From: "Kaartic Sivaraam"
On Tue, 2017-06-06 at 20:52 +0900, Junio C Hamano wrote:
"Waiting for the initial commit", or "No commits yet", can be
explained to describe the state of the current branch (not the state
of the repository), and it is correct that we do not have any commit
on the branch
On Tue, Jun 6, 2017 at 2:50 AM, Michael Haggerty wrote:
> On Mon, Jun 5, 2017 at 8:23 PM, Stefan Beller wrote:
>>
>> > [...]
>> > "git diff" has been taught to optionally paint new lines that are
>> > the same as deleted lines elsewhere differently from genuinely new
>> > lines.
>> >
>> > Are
Dear Sir,
Have a nice day!
We are interested in purchasing your products.Send your latest catalog,
also inform me about the Minimum order quantity, Delivery time or FOB,
and payment terms warranty.
Thanks and Best Regards,
Mr.Marco Plujm.
Phone: (+1) 703-684-5885
Fax: (+1) 703-684-0644
Washingt
Hi Jonathan,
On Fri, 2 Jun 2017, Jonathan Nieder wrote:
> Johannes Schindelin wrote:
> > On Thu, 1 Jun 2017, Stefan Beller wrote:
>
> >> We had a discussion off list how much of the test suite is in bad shape,
> >> and "$ git grep ^index" points out a lot of places as well.
> >
> > Maybe we shou
Jeffrey Walton writes:
> On Fri, Jun 2, 2017 at 2:30 AM, Davide Fiorentino
> wrote:
>> Is there a reason why you don't want or can't set those details?
>
> Well, they don't exist so there's nothing to set.
>
> The machine below its a CubieBoard used for testing. I remote into it
> with test@. As
Hi,
Johannes Schindelin wrote:
> On Fri, 2 Jun 2017, Jonathan Nieder wrote:
>> Johannes Schindelin wrote:
>>> Maybe we should call out a specific month (or even a longer period) during
>>> which we try to push toward that new hash function, and focus more on
>>> those tasks (and on critical bug f
On Tue, Jun 6, 2017 at 3:22 PM, Johannes Schindelin
wrote:
>> Thanks for offering. ;-)
>
> Undoubtedly my lack of command of the English language is to blame for
> this misunderstanding.
Sometimes it is best to not be a native speaker, just fluent enough to
get by. :)
> What I wanted to suggest
Stefan Beller wrote:
> On Tue, Jun 6, 2017 at 3:22 PM, Johannes Schindelin
> wrote:
>> In my mind, it would have made sense to ask well-respected cryptographers
>> about their opinions and then try to figure out a consensus among them (as
>> opposed to what I saw so far, a lot of enthusastic talk
Adam Dinwoodie writes:
> On Mon, Jun 05, 2017 at 11:42:31AM -0700, Stefan Beller wrote:
>> So I was wondering if there is a command that shows all trailers?
>> Similar to a "shortlog -sne" I would want to have a list of all trailers.
>> This is because there might be an even more popular trailer
On Tue, Jun 6, 2017 at 6:45 PM, Stefan Beller wrote:
> On Tue, Jun 6, 2017 at 3:22 PM, Johannes Schindelin
> wrote:
>>
>> 4) we still have the problem that there is no cryptography expert among
>> those who in the Git project are listened to
>
> I can assure you that Jonathan listened to crypto e
Jonathan Nieder writes:
>> 3) the only person who could make that call is Junio
>
> I strongly disagree with this.
If it helps, I _can_ make any set of declarations to make it sound
more official, e.g. (the remainder of) June is the "make sure our
tests are ready" month where we try to eradiate
Use modern style in the test t4005. Remove hard coded sha1 values.
Combine test prep work and the actual test. Rename the first
test to contain the word "setup".
Signed-off-by: Stefan Beller
---
Junio wrote:
> If it helps, I _can_ make any set of declarations to make it sound
> more official, e.
An empty string as a pathspec element matches all paths. A buggy
script, however, could accidentally assign an empty string to a
variable that then gets passed to a Git command invocation, e.g.:
path=... compute a path to be removed in $path ...
git rm -r "$path"
which would unintentio
This is configured to send via a gmail account
git send-email --to-cover --cc-cover
I See
Attempt to reload IO/Socket/SSL.pm aborted.
Compilation failed in require at
/usr/share/perl5/vendor_perl/Net/SMTP/SSL.pm line 6.
BEGIN failed--compilation aborted at
/usr/share/perl5/vendor_perl/Net/SMTP/SS
67 matches
Mail list logo
