From: Stefan Monnier <monnier@IRO.UMontreal.CA>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: emacs-devel@gnu.org
Subject: Re: BuGit
Date: Tue, 02 Feb 2016 17:06:55 -0500 [thread overview]
Message-ID: <jwv60y6hj0b.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <56B103C1.4050008@yandex.ru> (Dmitry Gutov's message of "Tue, 2 Feb 2016 22:30:09 +0300")
>> https://gitlab.com/monnier/bugit
>> It's still primitive (only the command-line UI and the email
>> notification system are more or less complete: the web UI is still
>> read-only, and there is no email UI at all).
> Looks like an interesting experiment.
> These lines look a bit contradictory to me:
>> ...the user can also share the same repository with the main project.
>> Every issue lives in its own branch named bugit/<id>.
> I imagine it might be uncomfortable working on a project which contains
> thousands of branches. You do a pull--and Git shows you all the remotes that
> have changed. With lots of branches, that would be a lot of output, even if
> you don't check them out locally.
Indeed. I don't have much experience with such a situation yet, but
I expect "branch-namespace-pollution" to be a problem.
Currently, for BuGit itself, I have 2 central repositories (one for the
code, one for the bug database), but I clone them into a shared local
repository. So when I do "git pull/push" I access the source repository
(and corresponding branches), and when I do "bugit sync" I access from
the bug repository (and corresponding branches).
That takes care of the use-case you mention, but it still leaves another
problem "git branch -a" includes all the bugit branches, which
is inconvenient. I haven't tried to solve this issue yet, but I'm
thinking of not sharing the local repository, and instead store the
local bugit repository in a subdirectory like .git/bugit.
> Not sure if there's an option to ignore only certain branches, for
> certain commands.
I use Git's support for multiple remote repositories for that.
Stefan
next prev parent reply other threads:[~2016-02-02 22:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-02 15:09 BuGit Stefan Monnier
2016-02-02 16:10 ` BuGit Aurélien Aptel
2016-02-02 16:43 ` BuGit Stefan Monnier
2016-02-03 10:37 ` BuGit Aurélien Aptel
2016-02-03 13:03 ` BuGit Stefan Monnier
2016-02-02 16:26 ` BuGit Nicolas Petton
2016-02-02 17:08 ` BuGit Stefan Monnier
2016-02-02 18:37 ` BuGit Aaron Conole
2016-02-02 19:40 ` BuGit Stefan Monnier
2016-02-02 19:30 ` BuGit Dmitry Gutov
2016-02-02 22:06 ` Stefan Monnier [this message]
2016-02-03 10:21 ` BuGit Aurélien Aptel
2016-02-03 13:04 ` BuGit Stefan Monnier
2016-02-03 16:45 ` BuGit John Wiegley
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jwv60y6hj0b.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=dgutov@yandex.ru \
--cc=emacs-devel@gnu.org \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).