I think I have identified an obscure bug. I have a reproducible test case.
I am trying to come up with enough of a test case that can be used for
finding and fixing the issue.
I have a set of patches. They are diffs. Some have whitespace issues.
(Which I believe triggers the bug.)
The patches go
> I think I have identified an obscure bug. I have a reproducible test case.
> I am trying to come up with enough of a test case that can be used for
> finding and fixing the issue.
BTW, I have tested this on 1.7.6.6 and 2.5.0. Same results on either version.
--
To unsubscribe from this list: sen
I help manage a Linux kernel repo for a large company. I have encountered
an odd problem that I think should not exist, but does.
At one point a merge was done from the development repo to the local
branch. Two of the existing commits have the same change to the same
location. At first glance they
I am trying to create an orphaned branch that contains the linux-3.12.y
branch from linux-stable. Each time I try a method to make this work I
encounter a blocker that halts my progress.
I expect that at least one of these is a bug, but I am not sure.
Here is what I did. I have read the docs and
> On Thu, Nov 05, 2015 at 01:16:54PM -0800, a...@clueserver.org wrote:
>
>> I created an orphan branch from 3.12-rc1. I then used git format-patch
>> to
>> generate patches from 3.12-rc1 to HEAD. (Over 7000 patches.) I use git
>> am
>> to apply them to the orphan branch. At patch 237 it fails to ap
The following describes bad behavior, but it is bad behavior that git-am
does not flag as bad. It just drops data silently.
I have a developer who has a patch that I am importing into git with
git-am. (Currently they have a quilt-like setup that is full of bad and
incomplete patches.)
At some po
code to revert back to the original code (which violates the
rule). Without this change I cannot detect this is an amend and reject the
change (unless --no-verify).
With this I can detect this is an amend and verify the patch as a whole
is not in violation of the rule.
Signed-off-by: Alan Clucas
On 14/09/15 15:47, Jeff King wrote:
On Mon, Sep 14, 2015 at 01:14:20PM +0100, Alan Clucas wrote:
Pass a single parameter 'amend' to the pre-commit hook when performing a
commit amend.
I think this is a sensible thing to want, and it has come up a few
times. I'm not sure why
git reset HEAD" on
each of the files, none of which I wanted to commit.
I searched the git-stash man page for this scenario, but found nothing
about it.
Surely staging all the files is a bug?
--
Alan Mackenzie (Nuremberg, Germany).
--
To unsubscribe from this list: send the line "unsu
Alan Mackenzie wrote: on Mon, 21 Dec 2015 14:29:54
> Hello, git project.
> Last night, whilst clearing out a stale "stash stack", I did "git stash
> pop". There were conflicts in two files.
> However, all the popped files became staged. This doesn'
Hello, Jeff.
On Tue, Dec 22, 2015 at 04:30:33AM -0500, Jeff King wrote:
> On Tue, Dec 22, 2015 at 09:17:38AM +0100, Dennis Kaarsemaker wrote:
> > On ma, 2015-12-21 at 14:29 +0000, Alan Mackenzie wrote:
> > > Hello, git project.
> > > Last night, whilst clearing out a
Hello, Jeff.
On Tue, Dec 29, 2015 at 02:53:30AM -0500, Jeff King wrote:
> On Thu, Dec 24, 2015 at 09:20:38AM +0000, Alan Mackenzie wrote:
> > > It seems to be a side effect of merge-recursive to stage the results,
> > > and in the no-conflict path we explicitly res
I am writing you this email to seek your cooperation and
partnership in a business that would benefit us immensely.
I would like to name you as 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
To quit gitk, I have to invoke ctrl-c from the command line. I get this
error when trying to quit gitk with ctrl-q or from the GUI menu:
--
☧
error writing "stdout": I/O error
error writing "stdout": I/O error
while executing
"puts "Error saving config: $err""
(procedure "savestuff" lin
Dear sir ,
I KELLY ALAN purchasing and sales manager of CFM INTERNATIONAL . Our
Company specialised in Supplying computer hardware and Electronic .We
want to extend our supplier list because of concurrency in prices on the
international market
We are seeking a supplier with whom we can to
fancy taking on this challenge? :)
[1] http://snapcraft.io/
[2] http://snapcraft.io/docs
[3] http://forum.snapcraft.io/
[4] https://snapcraft.io/docs/core/install
Best regards
--
Alan Pope
Snap Advocate
Canonical - Ubuntu Engineering and Services
+44 (0) 7973 620 164
alan.p...@canonical.com
http://ubuntu.com/
Hello,
I am Mr. Alan Austin, I am currently working with Credit suisse Bank London. I
saw your contact during my private search and I have a deep believe that you
will be very honest, committed and capable of assisting in this business
venture.
I am an account officer to late Dr. Manzoor
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
t be limited to just the
latest commits? That is, list commit X if and only if A is reachable
from X, B isn't reachable from X, and B is reachable from each of X's
children?
Thanks,
Alan Stern
--
To unsubscribe from this list: send the line "unsubscribe git"
On Tue, 18 Nov 2014, Jonathan Nieder wrote:
> Hi,
>
> Alan Stern wrote:
>
> > The "git rev-list A ^B" command lists all the commits that are
> > reachable from A but not from B. Is there a comparable command for the
> > converse relation, that is, a c
On Tue, 18 Nov 2014, Jonathan Nieder wrote:
> Alan Stern wrote:
>
> > Tracking down regressions. Bisection isn't perfect. Suppose a
> > bisection run ends up saying that B is the first bad commit. It's easy
> > enough to build B and test it, to verify that i
On Tue, 18 Nov 2014, Junio C Hamano wrote:
> Alan Stern writes:
>
> > On Tue, 18 Nov 2014, Jonathan Nieder wrote:
> >
> >> Alan Stern wrote:
> >>
> >> > Tracking down regressions. Bisection isn't perfect. Suppose a
> >> > b
On Tue, 18 Nov 2014, Junio C Hamano wrote:
> Alan Stern writes:
>
> >> > No. Here's a simple example:
> >> >
> >> > Y
> >> >/
> >> > /
> >> > X--B
> >> >
&
From: Alan Franzoni
Signed-off-by: Alan Franzoni
---
Documentation/date-formats.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/date-formats.txt b/Documentation/date-formats.txt
index ccd1fc8..284308a 100644
--- a/Documentation/date-formats.txt
+++ b
On Fri, Jun 27, 2014 at 12:08 AM, Robin Rosenberg
wrote:
> 1 hour in winter and 2 in summer, although some standards seem to say
> that summer time is really called CEST, computers apply DST to CET in summer.
>
> $ TZ=UTC date
> Tor 26 Jun 2014 22:08:01 UTC
>
> $ TZ=CET date
> Fre 27 Jun 2014 00:0
I tried using escaped globs with git mv, but globs don't seem to be
expanded with git mv.
So, for example, I've got files file1 & file2, and have been editing
them, so I've got file1~ and file2~ also, and *~ is in .gitignore.
If I do:
$ mkdir newdir
$ git mv file* newdir
I get a 'fatal: not in
keep as git command and use dpkg-divert to change
the other to another name to some other name?
--
Alan Chandler
http://www.chandlerfamily.org.uk
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to [EMAIL PROTECTED]
More majordomo inf
I found an interesting bug in git-format-patch.
Say you have a branch A. You create branch B and add a patch to it. You then
merge that patch into branch A. After the merge, some other process (we will
call it 'gerrit') uses annotate and changes the comment on the patch that
exists on branch B
example of what is happening here.
-Original Message-
From: Perry Hutchison [mailto:per...@pluto.rain.com]
Sent: Monday, November 26, 2012 8:15 PM
To: gits...@pobox.com
Cc: git@vger.kernel.org; Olsen, Alan R
Subject: Re: Interesting git-format-patch bug
Junio C Hamano wrote:
> &qu
I have found that if I add a remote and do a "git fetch -t -f remote_name" that
it *only* pulls tags.
Reading the man page it seems like it should pull all the remotes and all the
tags and the commits only reachable by tags.
Am I misreading this or it supposed to work this way. I don't mind do
PM
To: Olsen, Alan R
Cc: git@vger.kernel.org
Subject: Re: Fetch and -t
"Olsen, Alan R" writes:
> I have found that if I add a remote and do a "git fetch -t -f
> remote_name" that it *only* pulls tags.
>
> Reading the man page it seems like it should pull all the
31 matches
Mail list logo
