On Sun, Apr 17, 2016 at 04:10:28PM +0200, Andreas Schwab wrote:
> Andreas Mohr writes:
>
> > Unless I happened to misunderstand git's regex flavour, or something else...
> > (hmm, perhaps it's a try-match-single-line vs. multi-line content issue,
> > which perha
ot confirmed, then the question would be
what kind of potential documentation / usability weaknesses
successfully managed to lead me astray
and thus would need to be fixed.
Thanks,
Andreas Mohr
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...
[git-owner CC dutifully removed]
On Thu, Apr 16, 2015 at 05:48:42PM +0200, Johannes Schindelin wrote:
> Hi Peff,
>
> On 2015-04-16 17:28, Jeff King wrote:
> > On Thu, Apr 16, 2015 at 01:35:05PM +0200, Andreas Mohr wrote:
> >
> >> I strongly suspect that
On Thu, Apr 16, 2015 at 01:48:46PM +0200, Andreas Mohr wrote:
> OK, at this point in time it's my turn to actually verify
> that indeed it's NOT the virus scanner:
> - generate rebase-heavy activity
> - update
> - hit issue
> - unload virus (~ scanner?? I'm unsur
On Thu, Apr 16, 2015 at 01:42:35PM +0200, Andreas Mohr wrote:
> Hi,
>
> On Thu, Apr 16, 2015 at 01:31:02PM +0200, Johannes Schindelin wrote:
> > Hi,
> >
> > On 2015-04-16 13:10, Thomas Braun wrote:
> > > I've never had this issue. The error message
ptor scope handling issue in git source code is very easily
imaginable
- only a very rebase-heavy workflow of a sufficiently large repo
is likely to have this issue turn up in a frequently enough manner,
thus it's quite likely that it's not observed (or reported) all too often
Hi,
sorry, I had sent the prior mail prematurely (hit wrong key)
and have been busy working on the resubmission...
On Thu, Apr 16, 2015 at 01:10:36PM +0200, Thomas Braun wrote:
> Am 16.04.2015 um 12:03 schrieb Andreas Mohr:
> > Hi all,
> >
> > over the years I've ha
Hi all,
over the years I've had the same phenomenon with various versions of msysgit
(now at 1.9.5.msysgit.0, on Windows 7 64bit), so I'm now sufficiently
confident of it being a long-standing, longer-term issue and thus I'm
reporting it now.
Since I'm doing development in a sufficiently rebase-h
On Sat, Feb 09, 2013 at 03:35:35PM -0800, Junio C Hamano wrote:
> Andreas Mohr writes:
> > The main point of my mail was to stretch the (whether actually intended)
> > *perceived* start <-> stop symmetry
>
> Actually, in that sense, I do no think finish is exactly a go
mething quite similar to
the original HEAD (i.e., to finish - "stop" a started - bisect),
issue the following command:
Thanks a ton for your immediate handling of my wishlist item!
Andreas Mohr
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of
nged into
After a bisect session, to clean up the bisection state and
return to
the original HEAD (in other words, to "stop" bisect),
issue the following command:
$ git bisect reset
Andreas Mohr
--
GNU/Linux. It's not the software that's free,
11 matches
Mail list logo
