Is it (or would it be) possible to set the default strategy and strategy
options as provided by merge/rebase ``-s`` and ``-X`` in gitconfig?
I found myself comparing several conflicts using recursive's -Xpatience,
and in some cases the difference is quite staggering, changing from a
jumbled mess t
I'm trying to run git fetch using --shallow-since with a date range that
results in no commits to be selected.
In this scenario the command hangs indefinitely:
git fetch --shallow-since=2019-05-20 -vv
Server supports multi_ack_detailed
Server supports side-band-64k
Server supports ofs-delta
Serve
"git grep xxx" currently does not follow symlinks.
Please consider adding this functionality
Thx
YuriW
'm running git-2.9.0.
Regards,
Yuri
--
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
through http
$ git archive --format=tar
--remote=http://github.com/yurivict/vm-to-tor.git
fatal: Operation not supported by protocol.
git-2.6.2 on FreeBSD 10.2
Yuri
--
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 01/08/2015 08:52 AM, Kyle J. McKay wrote:
> Since --graph is text-based, this response may not be on-topic hence
> no cc: to the list.
I see --graph as an important tool to get an overview on how the
development is being done. I don't mind having a graphical tool for the
job, and I was even s
On 01/07/2015 04:47 PM, Johan Herland wrote:
> Have you looked at git show-branch --all?
I didn't. Helpful, but I need to get used to the output.
The first impression after looking at some random repository histories
is that it's still not what I had in mind, though.
--
To unsubscribe from this
Hi everyone,
git log --graph is hard for me to parse mentally when developing a
project which has a lot of branches.
All the tools I've been using seem to just parse log --graph's output,
and thus are no better at showing history.
I would love to have a graph mode where each branch is assigned a
On 11/30/2014 01:34 PM, Fredrik Gustafsson wrote:
> On Sun, Nov 30, 2014 at 01:18:34PM +0100, Yuri D'Elia wrote:
>> Is there a quick way to reproduce the effect of a shallow clone on a
>> local repository that doesn't involve filter-branch and/or re-clone?
>
> I&#
Hi everyone,
Is there a quick way to reproduce the effect of a shallow clone on a
local repository that doesn't involve filter-branch and/or re-clone?
My motivation is to reduce the local size of repositories I'm only
following, by trimming the history without prejudice to a [N] set of
last commi
borate and obscure reasoning
should be employed in the implementation
For me, if git would have told me that my pager doesn't support escape
sequences, I could have taken it from there.
Yuri
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to ma
for example. Such
'experimental' approach is maybe more reliable.
Yuri
--
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
ork,
have configure script check if the current PAGER supports colors and
build git accordingly?
configure could run the pager as one of its tests, and determine if
"ESC" appears on the output.
Yuri
--
To unsubscribe from this list: send the line "unsubscribe git" in
t
on size is made somewhere
in 'git diff' command.
Suggested behavior:
1. git should respect utf8, and in case of truncation it should add …
symbol.
2. truncation algorithm should read current terminal width and truncate
at width-1 length to allow for the above-mentioned symbol
Yuri
--
ed in most UNIX-like systems.
Yuri
--
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
s redundant and annoying. The
_uncommon_ case is the one Yuri hit: some library misconfiguration that
causes the helper not to run at all. Adding back any message is hurting
the common case to help the uncommon one.
But you can use the error code value to convey the cause of the failure
to git,
like this: MORE_DASH_R_WORKS This would be very accurate.
Not sure if this is an overkill for this issue.
Yuri
--
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
2013 -0400
I think that in a rare case of error this extra-printout wouldn't hurt.
I also made this message more user friendly, without mentioning the term
"helper".
Yuri
diff --git a/transport-helper.c b/transport-helper.c
index 2010674..5ea2831 100644
--- a/transport-helper.
On 01/16/2014 20:14, Jeff King wrote:
The second patch turns on "MORE=R" only for FreeBSD. Yuri, if you can
confirm that my patch works for you, that would be excellent. And if you
(or anyone) has access to NetBSD or OpenBSD to test the second patch on,
I'd welcome updates to c
aesthetic way is always good,
without making it look like a rainbow.
Yuri
--
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
ven more information with colors.
For example, make all dates which are less than 24 hours red.
Yuri
--
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
in general, so that git will work
fine for a new unchanged user?
Yuri
--
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
it print a wrong sequence? Is this because this is some kind of
linuxism that doesn't work on FreeBSD maybe?
Also, there are the termcap functions that allow to determine what does
the actual terminal supports. You should first check for cap bits
corresponding to the features you expect,
got
some error from the supporting libraries and didn't report it. I can't
tell now because I updated and the problem is gone.
Yuri
--
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
ake sure that any https errors (in this and other
locations) are reported to the user, and git never quits on error
without saying what the error is.
git-1.8.5.2
Yuri
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger
Thanks to everyone. The information was useful.
On 24 February 2013 21:31, Shawn Pearce wrote:
> On Sun, Feb 24, 2013 at 8:58 AM, Thomas Koch wrote:
>> Yuri Mikhailov:
>>> Dear Git community,
>>>
>>> I am a Software Developer and I have been using git for
26 matches
Mail list logo
