On Mon, May 19, 2014 at 10:46:21PM -0700, Jeremiah Mahler wrote:
Avoiding that is easy with an indirection, no? Something like this
at the top:
static const char *the_default_signature = git_version_string;
static const char *signature = the_default_signature;
and comparing
On Tue, May 20, 2014 at 01:49:31AM +, brian m. carlson wrote:
On Mon, May 19, 2014 at 07:28:17PM +0400, Alexey Shumkin wrote:
The tested encoding is always available in a variable. Use it instead of
hardcoding. Also, to be in line with other tests use ISO8859-1
(uppercase) rather then
On Mon, May 19, 2014 at 10:35:56PM +0300, Michael S. Tsirkin wrote:
I tried to fump the whole history of qemu with format-patch.
It crashes both with v2.0.0-rc2-21-g6087111
and with git 1.8.3.1:
~/opt/libexec/git-core/git-format-patch --follow -o patches/all
Signed-off-by: Matthieu Moy matthieu@imag.fr
---
Ram's patch lacks a test. Here it is. Fails without Ram's patch, and
passes with it.
Can be squashed into Ram's patch.
t/t3420-rebase-autostash.sh | 17 +
1 file changed, 17 insertions(+)
diff --git
On Tue, May 20, 2014 at 2:55 AM, Matthieu Moy matthieu@imag.fr wrote:
Signed-off-by: Matthieu Moy matthieu@imag.fr
---
Ram's patch lacks a test. Here it is. Fails without Ram's patch, and
passes with it.
Can be squashed into Ram's patch.
t/t3420-rebase-autostash.sh | 17
Signed-off-by: Matthieu Moy matthieu@imag.fr
---
Eric Sunshine sunsh...@sunshineco.com writes:
Simpler (replace above two lines):
test_set_editor $(pwd)/abort-editor.sh
Indeed.
And I had debug statements left.
Hopefully, this after-coffee-v2 will be clear enough and correct ;-).
Added option that allows a signature file to be used with format-patch
so that signatures with newlines and other special characters can be
easily included.
$ git format-patch --signature-file ~/.signature -1
The config variable format.signaturefile is also provided so that it
can be added by
v5 of patch to add format-patch --signature-file file option.
This revision includes more suggestions from Jeff King and Junio C Hamano:
- Use git_config_pathname instead of git_config_string for ~ expansion.
- Eliminated head/tail --lines which is not POSIX compliant.
Replaced with sed
On Tue, May 20, 2014 at 01:00:06AM -0700, Jeremiah Mahler wrote:
Added option that allows a signature file to be used with format-patch
so that signatures with newlines and other special characters can be
easily included.
$ git format-patch --signature-file ~/.signature -1
The config
On Tue, May 20, 2014 at 10:46 AM, Thomas Braun
thomas.br...@byte-physics.de wrote:
Am 19.05.2014 22:29, schrieb Erik Faye-Lund:
[...]
Would we need to wrap both ends, shouldn't wrapping only reading be
good enough to prevent deadlocking?
compat/poll/poll.c already contains a function called
When 'git remote rm' or 'git remote prune' were used in a repository
with many refs, and needed to delete many refs, a lot of time was spent
deleting those refs since for each deleted ref, repack_without_refs()
was called to rewrite packed-refs without just that deleted ref.
To avoid this, defer
When 'git remote prune' was used to delete many refs in a repository
with many refs, a lot of time was spent checking for (now) dangling
symbolic refs pointing to the deleted ref, since warn_dangling_symref()
was once per deleted ref to check all other refs in the repository.
Avoid this using the
The interaction with unary operators and operator precedence
for and || are better known than -a and -o, and for that
reason we prefer them. Replace all existing instances
of -a and -o to save readers from the burden of thinking
about such things.
Signed-off-by: Elia Pinto
The interaction with unary operators and operator precedence
for and || are better known than -a and -o, and for that
reason we prefer them. Replace all existing instances
of -a and -o to save readers from the burden of thinking
about such things.
Signed-off-by: Elia Pinto
The interaction with unary operators and operator precedence
for and || are better known than -a and -o, and for that
reason we prefer them. Replace all existing instances
of -a and -o to save readers from the burden of thinking
about such things.
Signed-off-by: Elia Pinto
The interaction with unary operators and operator precedence
for and || are better known than -a and -o, and for that
reason we prefer them. Replace all existing instances
of -a and -o to save readers from the burden of thinking
about such things.
Signed-off-by: Elia Pinto
These patch series convert test -a/-o to and ||.
This is the second version.
Changes:
- Modified commit comment based on Jonathan Nieder suggestions
(was don't use the -a or -o option with the test command)
- Modified patch on git-submodule.sh based on Jonathan Nieder suggestions
Elia
The interaction with unary operators and operator precedence
for and || are better known than -a and -o, and for that
reason we prefer them. Replace all existing instances
of -a and -o to save readers from the burden of thinking
about such things.
Signed-off-by: Elia Pinto
The interaction with unary operators and operator precedence
for and || are better known than -a and -o, and for that
reason we prefer them. Replace all existing instances
of -a and -o to save readers from the burden of thinking
about such things.
Signed-off-by: Elia Pinto
The interaction with unary operators and operator precedence
for and || are better known than -a and -o, and for that
reason we prefer them. Replace all existing instances
of -a and -o to save readers from the burden of thinking
about such things.
Signed-off-by: Elia Pinto
The interaction with unary operators and operator precedence
for and || are better known than -a and -o, and for that
reason we prefer them. Replace all existing instances
of -a and -o to save readers from the burden of thinking
about such things.
Signed-off-by: Elia Pinto
The interaction with unary operators and operator precedence
for and || are better known than -a and -o, and for that
reason we prefer them. Replace all existing instances
of -a and -o to save readers from the burden of thinking
about such things.
Signed-off-by: Elia Pinto
The interaction with unary operators and operator precedence
for and || are better known than -a and -o, and for that
reason we prefer them. Replace all existing instances
of -a and -o to save readers from the burden of thinking
about such things.
Signed-off-by: Elia Pinto
The interaction with unary operators and operator precedence
for and || are better known than -a and -o, and for that
reason we prefer them. Replace all existing instances
of -a and -o to save readers from the burden of thinking
about such things.
Signed-off-by: Elia Pinto
The interaction with unary operators and operator precedence
for and || are better known than -a and -o, and for that
reason we prefer them. Replace all existing instances
of -a and -o to save readers from the burden of thinking
about such things.
Signed-off-by: Elia Pinto
The interaction with unary operators and operator precedence
for and || are better known than -a and -o, and for that
reason we prefer them. Replace all existing instances
of -a and -o to save readers from the burden of thinking
about such things.
Signed-off-by: Elia Pinto
The interaction with unary operators and operator precedence
for and || are better known than -a and -o, and for that
reason we prefer them. Replace all existing instances
of -a and -o to save readers from the burden of thinking
about such things.
Signed-off-by: Elia Pinto
The interaction with unary operators and operator precedence
for and || are better known than -a and -o, and for that
reason we prefer them. Replace all existing instances
of -a and -o to save readers from the burden of thinking
about such things.
Signed-off-by: Elia Pinto
The interaction with unary operators and operator precedence
for and || are better known than -a and -o, and for that
reason we prefer them. Replace all existing instances
of -a and -o to save readers from the burden of thinking
about such things.
Signed-off-by: Elia Pinto
The interaction with unary operators and operator precedence
for and || are better known than -a and -o, and for that
reason we prefer them. Replace all existing instances
of -a and -o to save readers from the burden of thinking
about such things.
Signed-off-by: Elia Pinto
The interaction with unary operators and operator precedence
for and || are better known than -a and -o, and for that
reason we prefer them. Replace all existing instances
of -a and -o to save readers from the burden of thinking
about such things.
Signed-off-by: Elia Pinto
Signed-off-by: Ramsay Jones ram...@ramsay1.demon.co.uk
---
Hi Alexey,
If you need to re-roll your 'as/pretty-truncate' branch, could
you please squash the relevant parts of this patch into the
corresponding patches of your patch series. (ie this is a patch
against the head of the current pu
Elia Pinto gitter.spi...@gmail.com writes:
- test $status = D -o $status = T echo $sm_path
continue
+ {
+ test $status = D ||
+ test $status = T
+ }
+ echo $sm_path
Elia Pinto gitter.spi...@gmail.com writes:
Elia Pinto (19):
I went through the series (not very thoroughly) and it sounds good to
me.
--
Matthieu Moy
http://www-verimag.imag.fr/~moy/
--
To unsubscribe from this list: send the line unsubscribe git in
the body of a message to
On Tue, May 20, 2014 at 02:54:20PM +0100, Ramsay Jones wrote:
Signed-off-by: Ramsay Jones ram...@ramsay1.demon.co.uk
---
Hi Alexey,
If you need to re-roll your 'as/pretty-truncate' branch, could
you please squash the relevant parts of this patch into the
corresponding patches of your
On Tue, May 20, 2014 at 06:19:36PM +0400, Alexey Shumkin wrote:
On Tue, May 20, 2014 at 02:54:20PM +0100, Ramsay Jones wrote:
Signed-off-by: Ramsay Jones ram...@ramsay1.demon.co.uk
---
Hi Alexey,
If you need to re-roll your 'as/pretty-truncate' branch, could
you please squash
On Mon, May 19, 2014 at 02:34:26PM -0700, Junio C Hamano wrote:
Michael S. Tsirkin m...@redhat.com writes:
test ack! handling
Signed-off-by: Michael S. Tsirkin m...@redhat.com
Will queue with this squashed in.
4/4 seems to have some style issues as well, but I didn't look very
Am 5/20/2014 15:50, schrieb Elia Pinto:
# If we don't already have a -f flag and the submodule
has never been checked out
- if test -z $subsha1 -a -z $force
+ if test -z $subsha1 || test -z $force
Should not be ||, but !
Added in 0a144b3 (t4205, t6006: add failing tests for the case when
i18n.logOutputEncoding is set, 2014-05-19) tests give no error
(somehow) with Bash as /bin/sh but fail for some other shells.
Quote format strings to avoid errors.
Signed-off-by: Alexey Shumkin alex.crez...@gmail.com
On 05/19/2014 11:31 PM, Junio C Hamano wrote:
Felipe Contreras felipe.contre...@gmail.com writes:
Junio C Hamano wrote:
After looking at the reverse-depends list of packages, my faith is
strengthened in that the Git ecosystem is truly maturing and useful
third-party plug-ins will be picked
On 20/05/14 15:19, Alexey Shumkin wrote:
On Tue, May 20, 2014 at 02:54:20PM +0100, Ramsay Jones wrote:
Signed-off-by: Ramsay Jones ram...@ramsay1.demon.co.uk
---
Hi Alexey,
If you need to re-roll your 'as/pretty-truncate' branch, could
you please squash the relevant parts of this patch
On 20/05/14 15:48, Alexey Shumkin wrote:
Added in 0a144b3 (t4205, t6006: add failing tests for the case when
i18n.logOutputEncoding is set, 2014-05-19) tests give no error
(somehow) with Bash as /bin/sh but fail for some other shells.
Quote format strings to avoid errors.
Signed-off-by:
Jeff King p...@peff.net writes:
You could do:
#define DEFAULT_SIGNATURE git_version_string
static const char *signature = DEFAULT_SIGNATURE;
...
if (signature == DEFAULT_SIGNATURE)
...
but maybe that is getting a little unwieldy, considering the scope of
the original
Michael S. Tsirkin m...@redhat.com writes:
Just to clarify I can post v2 of 4/4 without reposting 1-3 since they
are queued?
If you need to update anything queued only on 'pu' but not yet in
'next', it is customary to resend the whole for everybody to see
(what is already in 'next' should only
On Tue, May 20, 2014 at 4:55 PM, Michael Haggerty mhag...@alum.mit.edu wrote:
On 05/19/2014 11:31 PM, Junio C Hamano wrote:
Felipe Contreras felipe.contre...@gmail.com writes:
Where is git-imerge packaged?
I didn't see it on the archive the said Ubuntu box slurps from, but
I did not check
Can GIT handle versioning of large 20+ GB files in a directory?
Lou Stewart
AOCWS Software Configuration Management
757-269-2388
--
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
On Tue, May 20, 2014 at 04:01:22PM +0100, Ramsay Jones wrote:
On 20/05/14 15:19, Alexey Shumkin wrote:
On Tue, May 20, 2014 at 02:54:20PM +0100, Ramsay Jones wrote:
Signed-off-by: Ramsay Jones ram...@ramsay1.demon.co.uk
---
Hi Alexey,
If you need to re-roll your
I was following some tutorial (http://gitref.org/branching/#merge) - and doing
it in my console :
Arup-iMac:arup_git shreyas$ git status
# On branch master
nothing to commit, working directory clean
Arup-iMac:arup_git shreyas$ touch test.rb
Arup-iMac:arup_git shreyas$ ls
git_1.txttest.rb
On 20/05/14 17:02, Alexey Shumkin wrote:
On Tue, May 20, 2014 at 04:01:22PM +0100, Ramsay Jones wrote:
On 20/05/14 15:19, Alexey Shumkin wrote:
On Tue, May 20, 2014 at 02:54:20PM +0100, Ramsay Jones wrote:
Signed-off-by: Ramsay Jones ram...@ramsay1.demon.co.uk
---
Hi Alexey,
If you need
The files in question would be in directory containing many files some small
other huge (example: text files, docs,and jpgs are Mbs, but executables and ova
images are GBs, etc).
Lou
From: Gary Fixler [mailto:gfix...@gmail.com]
Sent: Tuesday, May 20, 2014 12:09 PM
To: Stewart, Louis (IS)
Cc:
On 5/20/2014 10:38 AM, Arup Rakshit wrote:
I was following some tutorial (http://gitref.org/branching/#merge) - and doing
it in my console :
Arup-iMac:arup_git shreyas$ git status
# On branch master
nothing to commit, working directory clean
Arup-iMac:arup_git shreyas$ touch test.rb
On Tuesday, May 20, 2014 11:56:57 AM you wrote:
On 5/20/2014 10:38 AM, Arup Rakshit wrote:
I was following some tutorial (http://gitref.org/branching/#merge) - and
doing it in my console :
Because you never committed the original file to the master branch
before you created and switched
-Original Message-
From: Stewart, Louis (IS)
Sent: Tuesday, May 20, 2014 11:38
Can GIT handle versioning of large 20+ GB files in a directory?
Are you asking 20 files of a GB each or files 20GB each?
A what and why may help with the underlying questions.
v/r,
Jason Pyeron
--
On 5/20/2014 11:03 AM, Arup Rakshit wrote:
On Tuesday, May 20, 2014 11:56:57 AM you wrote:
On 5/20/2014 10:38 AM, Arup Rakshit wrote:
I was following some tutorial (http://gitref.org/branching/#merge) - and
doing it in my console :
Because you never committed the original file to the
On 5/20/2014 10:37 AM, Stewart, Louis (IS) wrote:
Can GIT handle versioning of large 20+ GB files in a directory?
Maybe you're looking for git-annex?
https://git-annex.branchable.com/
--
.marius
--
To unsubscribe from this list: send the line unsubscribe git in
the body of a message to
Alexey Shumkin alex.crez...@gmail.com writes:
AFAIU, Junio already applied my patches (existance of a branch
as/pretty-truncate tells us that). So, we can only send other patches that
fix errors brought with former patches.
No, NO, NO
The existence of a branch merely means that I saw
Stewart, Louis (IS) louis.stew...@ngc.com writes:
Can GIT handle versioning of large 20+ GB files in a directory?
I think you can git add such files, push/fetch histories that
contains such files over the wire, and git checkout such files,
but naturally reading, processing and writing 20+GB
Thanks for the reply. I just read the intro to GIT and I am concerned about
the part that it will copy the whole repository to the developers work area.
They really just need the one directory and files under that one directory. The
history has TBs of data.
Lou
-Original Message-
Anders Kaseorg ande...@mit.edu writes:
How bad does the documentation look with the patch applied (I know how
bad it looks without source-highlight installed)? If it is not too bad,
then it sounds like a sensible solution to drop the highlight markup
unconditionally like the patch that
Matthieu Moy matthieu@grenoble-inp.fr writes:
[ Cc-ing Ramkumar ]
Karen Etheridge et...@cpan.org writes:
scenario:
- edit some tracked files; do not add them to the index
- git config rebase.autostash true
- git rebase -i HEAD~3 (an autostash will be created)
- delete the entire
Jeff King p...@peff.net writes:
On Mon, May 19, 2014 at 10:35:56PM +0300, Michael S. Tsirkin wrote:
I tried to fump the whole history of qemu with format-patch.
It crashes both with v2.0.0-rc2-21-g6087111
and with git 1.8.3.1:
~/opt/libexec/git-core/git-format-patch --follow -o
Jeff King p...@peff.net writes:
But one could easily specify a longer, multi-line signature,
like:
git format-patch --signature='
this is my long signature
it has multiple lines
' ...
We should notice that it already has its own trailing
newline, and suppress one of ours.
Elia Pinto gitter.spi...@gmail.com writes:
These patch series convert test -a/-o to and ||.
This is the second version.
Perhaps slightly off-topic, but has the remainder of the previous $(...)
series been perfected and ready to apply?
--
To unsubscribe from this list: send the line
Elia Pinto gitter.spi...@gmail.com writes:
The interaction with unary operators and operator precedence
for and || are better known than -a and -o, and for that
reason we prefer them. Replace all existing instances
of -a and -o to save readers from the burden of thinking
about such things.
Stewart, Louis (IS) louis.stew...@ngc.com writes:
Thanks for the reply. I just read the intro to GIT and I am
concerned about the part that it will copy the whole repository to
the developers work area. They really just need the one directory
and files under that one directory. The history
From you response then there is a method to only obtain the Project, Directory
and Files (which could hold 80 GBs of data) and not the rest of the Repository
that contained the full overall Projects?
-Original Message-
From: Junio C Hamano [mailto:gits...@pobox.com]
Sent: Tuesday, May
On Tuesday, May 20, 2014 12:06:49 PM you wrote:
It never came to the new branch, as it was never version controlled,
it was an untracked file left behind when you switched branches.
Once you added it to the new branch, change_class, it became a version
controlled file,
This is still
Hi,
Elia Pinto wrote:
These patch series convert test -a/-o to and ||.
Should this come with a new check in t/check-non-portable-shell.pl so
we don't regress in the future?
Elia Pinto (19):
[...]
check_bindir|2 +-
contrib/examples/git-clone.sh |2 +-
Arup Rakshit arupraks...@rocketmail.com writes:
On Tuesday, May 20, 2014 12:06:49 PM you wrote:
It never came to the new branch, as it was never version controlled,
it was an untracked file left behind when you switched branches.
Once you added it to the new branch, change_class, it
On Tue, May 20, 2014 at 10:53:11AM -0700, Junio C Hamano wrote:
I actually think these supress extra LFs trying to be overly smart
and inviting unnecessary surprises. Unlike log messages people type
(in which we do squash runs of blank lines and other prettifying),
mail-signature string is
Am Dienstag, den 20.05.2014, 17:24 + schrieb Stewart, Louis (IS):
Thanks for the reply. I just read the intro to GIT and I am concerned
about the part that it will copy the whole repository to the developers
work area. They really just need the one directory and files under
that one
On 5/20/2014 12:20 PM, Arup Rakshit wrote:
On Tuesday, May 20, 2014 12:06:49 PM you wrote:
It never came to the new branch, as it was never version controlled,
it was an untracked file left behind when you switched branches.
Once you added it to the new branch, change_class, it became a
Matthieu Moy matthieu@imag.fr writes:
Signed-off-by: Matthieu Moy matthieu@imag.fr
---
Eric Sunshine sunsh...@sunshineco.com writes:
Simpler (replace above two lines):
test_set_editor $(pwd)/abort-editor.sh
Indeed.
And I had debug statements left.
Hopefully, this
Richard Hansen rhan...@bbn.com writes:
Not all shells subject the prompt string to parameter expansion. Test
whether the shell will expand the value of PS1, and use the result to
control whether raw ref names are included directly in PS1.
This fixes a regression introduced in commit 8976500
On Tuesday, May 20, 2014 11:24:11 AM you wrote:
Arup Rakshit arupraks...@rocketmail.com writes:
Untracked files and modifications to files in your working directory
do not belong to your current branch. This is to allow you, after
starting to work on one branch then realizing that the
On 5/20/2014 12:40 PM, Arup Rakshit wrote:
On Tuesday, May 20, 2014 11:24:11 AM you wrote:
Arup Rakshit arupraks...@rocketmail.com writes:
Untracked files and modifications to files in your working directory
do not belong to your current branch. This is to allow you, after
starting to work on
Jeff King p...@peff.net writes:
If it were just --signature, I'd agree. After all, nobody is even
complaining. But this is also in preparation for --signature-file.
Should the user create a file without a trailing newline?
Ahh, I missed that part.
I am fine with processing it with
Junio C Hamano gits...@pobox.com writes:
As I already said, I think better known is much less of an issue
than that -a/-o is more error prone, and that is the reason why
we may want to do this rewrite.
I do not know offhand how busy the tree would be when we can apply
these patches
Stepan Kasal ka...@ucw.cz writes:
From: Cezary Zawadka czawa...@gmail.com
Date: Tue, 13 Jul 2010 16:17:43 +0200
[efl: moved MinGW-specific part to compat/]
[jes: fixed compilation on non-Windows]
Eric Sunshine fixed mingw_offset_1st_component() to return consistently foo
for UNC
On Tue, 20 May 2014 18:18:08 +
Stewart, Louis (IS) louis.stew...@ngc.com wrote:
From you response then there is a method to only obtain the Project,
Directory and Files (which could hold 80 GBs of data) and not the
rest of the Repository that contained the full overall Projects?
Please
This is the POSIX port of the patches I typically use to track down msysgit
performance issues (thus v4, the latest windows-only version is here [1]).
Sebastian and Dscho thought this might be useful in core git, so here it is.
[1] https://github.com/msysgit/git/pull/46
Karsten Blees (3):
add
Add trace_performance and trace_performance_since macros that print file
name, line number, time and an optional printf-formatted text to the file
specified in environment variable GIT_TRACE_PERFORMANCE.
Unless enabled via GIT_TRACE_PERFORMANCE, these macros have no noticeable
impact on
Add a getnanotime() function that returns nanoseconds since 01/01/1970 as
unsigned 64-bit integer (i.e. overflows in july 2554). This is easier to
work with than e.g. struct timeval or struct timespec.
The implementation uses gettimeofday() by default; supports high precision
time sources on the
Add performance tracing to identify which git commands are called and how
long they execute. This is particularly useful to debug performance issues
of scripted commands.
Usage example: GIT_TRACE_PERFORMANCE=~/git-trace.log git stash list
Creates a log file like this:
performance: at
Hello,
On Tue, May 20, 2014 at 11:57:56AM -0700, Junio C Hamano wrote:
It would be nice if somebody in the S-o-b chain can double-check
that the combined version is sane. [...]
Combined was an unfortunate word. There was a pair of successive
commits in msysgit all the time. I just decided
Jens Lindström j...@opera.com writes:
When 'git remote rm' or 'git remote prune' were used in a repository
with many refs, and needed to delete many refs, a lot of time was spent
deleting those refs since for each deleted ref, repack_without_refs()
was called to rewrite packed-refs without
Stepan Kasal ka...@ucw.cz writes:
Hello,
On Tue, May 20, 2014 at 11:57:56AM -0700, Junio C Hamano wrote:
It would be nice if somebody in the S-o-b chain can double-check
that the combined version is sane. [...]
Combined was an unfortunate word. There was a pair of successive
commits in
Ronnie Sahlberg wrote:
Wrap all the ref updates inside a transaction to make the update atomic.
Interesting.
[...]
--- a/builtin/receive-pack.c
+++ b/builtin/receive-pack.c
@@ -46,6 +46,8 @@ static void *head_name_to_free;
static int sent_capabilities;
static int shallow_update;
Junio C Hamano gits...@pobox.com writes:
A bit safer way to organize might be to first create a list of the
refs to be removed in-core, update packed-refs without these refs to
be removed, and then finally remove the loose ones, but I haven't
thought things through.
Perhaps a removal of
On Tue, May 20, 2014 at 12:42 PM, Jonathan Nieder jrnie...@gmail.com wrote:
Ronnie Sahlberg wrote:
Wrap all the ref updates inside a transaction to make the update atomic.
Interesting.
[...]
--- a/builtin/receive-pack.c
+++ b/builtin/receive-pack.c
@@ -46,6 +46,8 @@ static void
Ronnie Sahlberg wrote:
[Subject: fast-import.c: use a ref transaction when dumping tags]
This seems like an odd thing to do: either it would make sense to have
a single transaction for all imported refs so all fail or succeed
together, or there would be separate transactions for each ref.
That
Junio C Hamano wrote:
Felipe Contreras felipe.contre...@gmail.com writes:
Junio C Hamano wrote:
2. add warning that is given every time the scripts are run and
give the same instruction as in README.
3. (optional) cripple the script to make them always fail after
On Tue, May 20, 2014 at 1:38 PM, Jonathan Nieder jrnie...@gmail.com wrote:
Ronnie Sahlberg wrote:
[Subject: fast-import.c: use a ref transaction when dumping tags]
This seems like an odd thing to do: either it would make sense to have
a single transaction for all imported refs so all fail or
Junio C Hamano wrote:
Felipe Contreras felipe.contre...@gmail.com writes:
Junio C Hamano wrote:
After looking at the reverse-depends list of packages, my faith is
strengthened in that the Git ecosystem is truly maturing and useful
third-party plug-ins will be picked up by distro
Felipe Contreras felipe.contre...@gmail.com writes:
Let's try this in a different way, as I sense there is a
misunderstanding somewhere about your wish.
...
No, I already said I do not want the code removed from v2.0, that's why
I sent patches that simply added a warning, and I specifically
Junio C Hamano wrote:
Felipe Contreras felipe.contre...@gmail.com writes:
...
Which will generate the integration instructions for you:
% git reintegrate --cat
base master
merge jl/submodule-mv
Moving a regular file in a repository with a .gitmodules file was
Signed-off-by: Ramsay Jones ram...@ramsay1.demon.co.uk
---
The test suite has been failing for me on the pu branch for
a while now. I finally found a few minutes to take a look.
This failure is specific to the dash shell (/bin/sh) on my
system (ie it may well affect other shells, but I haven't
Felipe Contreras felipe.contre...@gmail.com writes:
Or have an option to specify a dynamic instruction sheet, so you can cat
the instructions of 'match-next' and replace the base. However, I don't
see the point of re-applying the branches for 'next' if you already know
that 'next' and
Ramsay Jones ram...@ramsay1.demon.co.uk writes:
This patch is an RFC, because I take a different approach to the
above solution, only because the diff is much smaller and easier
to read! Is it a better solution?
ATB,
Ramsay Jones
t/t-basic.sh | 15 +--
1 file changed, 9
Junio C Hamano wrote:
Felipe Contreras felipe.contre...@gmail.com writes:
Let's try this in a different way, as I sense there is a
misunderstanding somewhere about your wish.
...
No, I already said I do not want the code removed from v2.0, that's why
I sent patches that simply added a
1 - 100 of 126 matches
Mail list logo
