On 06/28/2016 09:17 AM, Matthieu Moy wrote:
> "Andy Falanga (afalanga)" <afala...@micron.com> writes:
>
>> After the line calling increlnum is executed, I often have issues with
>> make unable to spawn the next command because it can't read the current
>>
Hi,
I'm using git version 1.8.3.1. I have a process for building RPMs in my
repository. The RPMs are versioned using a "build number". In order to
maintain uniqueness for this build number, I have stored this number to
a file which exists on only a unique branch.
The build process, for an
, the update-index operation you indicated will
not change index membership at all, but will simply resync the index
members with actual working tree files.
So I think now that the script should do "update-index --refresh"
followed by "diff-index --quiet HEAD". Sound correct?
to achieve what I'm after, I'd appreciate
a tip. Otherwise I'll just change the comments explaining why there's
a "diff" in my script.
andy
> 5. git diff correctly reports no changes 6. git diff-index now also
> reports nothing This is working as designed (though I agree it is a l
. This is stable behavior until next step
5. git diff correctly reports no changes
6. git diff-index now also reports nothing
My understanding is that git diff-index should care only about content
and file mode, not modification time.
===
andy
On Mon, Jan 4, 2016 at 12:31 PM, Junio C Hamano <gits...@pobox.com> wrote:
> Andy Lutomirski <l...@amacapital.net> writes:
>
>> git bisect run is great, but it's not so great when the test process
>> is "sudo make modules_install && sudo make install &a
On Wed, Dec 30, 2015 at 12:09 PM, Junio C Hamano <gits...@pobox.com> wrote:
> Andy Lutomirski <l...@kernel.org> writes:
>
>> I'm currently bisecting a Linux bug on my laptop. The starting good
>> commit is v4.4-rc3 and the starting bad commit is v4.4-rc7.
>>
be that, rather than testing commits in
between the good and bad commits, it would test the result of merging
those commits with v4.4-rc3.
Obviously the syntax could be tweaked a lot, but I think the concept
could be quite handy.
Thanks,
Andy
--
To unsubscribe from this list: send the line "unsubscrib
see RFC 2822
section 3.4, which defines mailbox and mailbox-list as well as section
3.2.6, which indicates that a phrase can contain a quoted-string.
--Andy
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo
On Tue, 2015-10-13 at 14:11 -0700, Junio C Hamano wrote:
> Andy Shevchenko <andriy.shevche...@linux.intel.com> writes:
>
> > My often use case is to do:
> > % git format-patch --cover-letter --subject-prefix="PATCH
> > vN" rev1^..revXYZ
> >
quot;
rev1^..revXYZ
P.S. Going further we can even introduce something like --valid-cmd to
send-email to run, for example, checkpatch.pl.
Signed-off-by: Andy Shevchenko <andriy.shevche...@linux.intel.com>
---
git-send-email.perl | 5 -
1 file changed, 4 insertions(+), 1 deletion
Is apparently a known issue.
Here is a temp fix : https://github.com/git-for-windows/git/issues/376
--
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
without any warnings or other fanfare.
--Andy
diff --git a/archive-tar.c b/archive-tar.c
index 719b629..c6bf7e4 100644
--- a/archive-tar.c
+++ b/archive-tar.c
@@ -2,6 +2,8 @@
* Copyright (c) 2005, 2006 Rene Scharfe
*/
#include cache.h
+#include tree.h
+#include object.h
#include tar.h
#include
'a/*.txt' did not match any file(s) known to git.
Signed-off-by: Andy Spencer andy753...@gmail.com
---
tree-walk.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tree-walk.c b/tree-walk.c
index 5ece8c3..e06f240 100644
--- a/tree-walk.c
+++ b/tree-walk.c
@@ -743,7 +743,7
On Thu, Jan 9, 2014 at 12:11 PM, Junio C Hamano gits...@pobox.com wrote:
Andy Lutomirski l...@amacapital.net writes:
It's possible, in principle, to shove enough metadata into the output
of 'git archive' to allow anyone to verify (without cloning the repo)
to verify that the archive
On Thu, Jan 9, 2014 at 2:46 PM, Junio C Hamano gits...@pobox.com wrote:
Andy Lutomirski l...@amacapital.net writes:
You only need the object name of the top-level tree. After untar
the archive into an empty directory, make it a new repository and
git add . git write-tree---the result should
.)
--Andy
--
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
script in every
new repository is wasteful and leaves you with potentially out-of-date scripts
when you update git.
Andy
--
Dr Andy Parkins
andypark...@gmail.com
--
To unsubscribe from this list: send the line unsubscribe git in
the body of a message to majord...@vger.kernel.org
More majordomo
On Tuesday 12 February 2013 09:01:14 Michael Haggerty wrote:
I assume you are the Andy Parkins who originally submitted
post-commit-email to the Git project...
I am indeed. Hello.
I have derived another script from yours:
https://github.com/mhagger/git-multimail
I affixed
).
If somebody can explain what license the code is under and how they come
to that conclusion, I would be very grateful.
And if Andy Parkins (the original author) is listening, please indicate
whether you had any intent *other* than GPLv2.
I intended it to be under the same license as Git. I had read
is with the git client as well because of the
modified time. If it were pulled then the modified time would've
changed, so it must have been taken from an earlier commit on my local
branch.
Did you git rm the 'old' name of the folder?
Andy
--
To unsubscribe from this list: send the line unsubscribe
, but is
it the proper way? If not, what is?
The easiest answer to this is run 'git status'. It'll list the files in
various states, and tell you how to undo the changes.
Andy
--
To unsubscribe from this list: send the line unsubscribe git in
the body of a message to majord...@vger.kernel.org
More
on
the probabilities) that there was some error in your testing.
-andy
-
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
23 matches
Mail list logo
