all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Dmitry Gutov <dgutov@yandex.ru>
To: Gary Oberbrunner <garyo@oberbrunner.com>
Cc: emacs-devel@gnu.org
Subject: Re: project.el: git submodules?
Date: Tue, 12 May 2020 22:28:00 +0300	[thread overview]
Message-ID: <21d66bf4-5cae-56b7-5c59-9257e887b672@yandex.ru> (raw)
In-Reply-To: <CAFChFyjN34qLaEksBcptQXcevLTuMqK45OYcCvCBFt8GCLyYEg@mail.gmail.com>

On 12.05.2020 21:33, Gary Oberbrunner wrote:
> In my case at least, you're right and my submodule is seriously
> confused. It has a .git/ dir which disagrees with the ../.git/modules
> one. That's what was causing my problem. I've been doing a lot of work
> in that submodule (multiple upstream repos, merges, pushes, etc.) and
> perhaps something I did made it create that.

How common do you think is such problem going to be? If it's rare, I'd 
rather let you fix the local configuration and leave that part of the 
code in Emacs simple. Unless this comes up again, of course.

> Apparently the correct way to do this is "git rev-parse
> --show-superproject-working-tree". See
> https://stackoverflow.com/questions/7359204  for more info. (And in
> fact that does work in my case even with my messed-up .git dir in the
> submodule.)

Thank you. Any idea which version of Git this was added in first? We'd 
have to consider that for compatibility with older systems.



  reply	other threads:[~2020-05-12 19:28 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-12 15:31 project.el: git submodules? Gary Oberbrunner
2020-05-12 15:53 ` Dmitry Gutov
2020-05-12 18:05   ` Michael Welsh Duggan
2020-05-12 18:27     ` Dmitry Gutov
2020-05-12 19:36       ` Stefan Monnier
2020-05-12 19:39         ` Dmitry Gutov
2020-05-12 20:45         ` Michael Welsh Duggan
2020-05-12 20:53           ` Dmitry Gutov
2020-05-12 21:04             ` Stefan Monnier
2020-05-12 21:06               ` Dmitry Gutov
2020-05-12 21:09                 ` Stefan Monnier
2020-05-14  0:32                   ` Dmitry Gutov
2020-05-14  2:55                     ` Stefan Monnier
2020-05-14 15:04                       ` Dmitry Gutov
2020-05-14 17:57                         ` Stefan Monnier
2020-05-14 19:29                           ` Dmitry Gutov
2020-05-14 20:01                             ` Stefan Monnier
2020-05-14 20:13                               ` Dmitry Gutov
2020-05-14 21:17                                 ` Dmitry Gutov
2020-05-14 21:38                                   ` Michael Welsh Duggan
2020-05-15  1:21                                     ` Dmitry Gutov
2020-05-15  5:11                                       ` Dmitry Gutov
2020-05-15  7:40                                         ` Kévin Le Gouguec
2020-05-15 19:17                                           ` Dmitry Gutov
2020-05-12 20:53           ` Michael Welsh Duggan
2020-05-12 20:51       ` Michael Welsh Duggan
2020-05-12 20:58     ` John Yates
2020-05-13  7:19       ` Andreas Schwab
2020-05-12 18:33   ` Gary Oberbrunner
2020-05-12 19:28     ` Dmitry Gutov [this message]
2020-05-12 19:34       ` Gary Oberbrunner
2020-05-12 19:41         ` Dmitry Gutov
2020-05-12 19:44     ` Doug Davis
2020-05-12 19:50       ` Gary Oberbrunner

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=21d66bf4-5cae-56b7-5c59-9257e887b672@yandex.ru \
    --to=dgutov@yandex.ru \
    --cc=emacs-devel@gnu.org \
    --cc=garyo@oberbrunner.com \
    /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.