all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: 15365@debbugs.gnu.org
Subject: bug#15365: 24.3.50; Segfault when calling vc-git-log-edit-toggle-amend
Date: Sat, 14 Sep 2013 16:29:02 +0300	[thread overview]
Message-ID: <83vc23fs69.fsf@gnu.org> (raw)
In-Reply-To: <52345F17.6000002@yandex.ru>

> Date: Sat, 14 Sep 2013 16:05:27 +0300
> From: Dmitry Gutov <dgutov@yandex.ru>
> CC: 15365@debbugs.gnu.org
> 
> On 14.09.2013 11:02, Eli Zaretskii wrote:
> > If you can reproduce this with bzr (I tried, but couldn't), please
> > show the recipe.
> 
> There's no point trying, vc-bzr doesn't have a corresponding command.

Yes, but I didn't know that until I tried.

> > I have a number of local bzr repositories, and can
> > create new ones at will, so I can use them for testing.  For any other
> > VCS, I have only remote repositories on my machine, and I don't dare
> > to run such tests for a remote repo.  If you can set up some scratch
> > git repo for me at some URL, I will try using that to work on this
> > bug.
> 
> Why scratch?

Because it could be messed up by the testing.

> Since we're talking about a DVCS, you'd have to have a local repository 
> clone to interact with it. So you'll end up with a local repo anyway.

I don't know how to make sure my commits are never pushed.  I'm simply
too afraid of git, sorry.  I have a very simple workflow, which works
with a couple of git repositories I need to track for the projects
that use it to which I contribute.  It took me a while to set up that
workflow, including a couple of aliases I needed to keep me sane, and
I'm trying very hard not to deviate from that workflow.

> > And yes, I try to stay away of git, and only use a handful of commands
> > with it.  There are already people here whose refusal to use bzr is
> > silently tolerated, so I don't see why my desire not to touch git any
> > more than I have to should be met with a different reaction.
> 
> I don't think any of the people you mention are considered core 
> contributors.

I don't see the importance of this distinction: committing from git,
or even using git, is not a requirement for core contributors to
Emacs, except for Elpa.

> > Thanks, this was "the missing link".  Please try running with the
> > following change for a while, and see if it avoids the aborts, and
> > does not produce any other redisplay problems:
> 
> Thank you, the crash seems to be fixed, no new problems so far.

Thanks.  Let's wait for a few days, and if you see no adverse effects,
I will commit the changes.





  reply	other threads:[~2013-09-14 13:29 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-13 11:55 bug#15365: 24.3.50; Segfault when calling vc-git-log-edit-toggle-amend Dmitry Gutov
2013-09-13 13:18 ` Eli Zaretskii
2013-09-14  1:12   ` Dmitry Gutov
2013-09-14  8:02     ` Eli Zaretskii
2013-09-14  8:34       ` martin rudalics
2013-09-14  8:59         ` Eli Zaretskii
2013-09-14  9:47           ` martin rudalics
2013-09-14 10:16             ` Eli Zaretskii
2013-09-14 13:08               ` Dmitry Gutov
2013-09-14 13:45                 ` Eli Zaretskii
2013-09-15  3:01                   ` Dmitry Gutov
2013-09-15  6:20                     ` Eli Zaretskii
2013-09-15 14:53                       ` Dmitry Gutov
2013-09-14 13:05       ` Dmitry Gutov
2013-09-14 13:29         ` Eli Zaretskii [this message]
2013-09-19  8:23           ` Eli Zaretskii
2013-09-22  5:00             ` Dmitry Gutov
2013-09-22  7:14               ` Eli Zaretskii
2013-09-14 14:37         ` Stefan Monnier

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83vc23fs69.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=15365@debbugs.gnu.org \
    --cc=dgutov@yandex.ru \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.