git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Felipe Contreras <felipe.contreras@gmail.com>
To: Max Horn <max@quendi.de>
Cc: John Keeping <john@keeping.me.uk>,
	git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>,
	Jeff King <peff@peff.net>
Subject: Re: [PATCH 00/13] remote-hg: general updates
Date: Thu, 4 Apr 2013 00:46:47 -0600	[thread overview]
Message-ID: <CAMP44s3HcLji22JDoSVZG_cLca8LXTbUPuVv8SbAM1yTqn8zcw@mail.gmail.com> (raw)
In-Reply-To: <CAMP44s3qAPJtNVsb4gvYd1PunN4c-crxpVJc0K9520eiBO8iwA@mail.gmail.com>

On Thu, Apr 4, 2013 at 12:42 AM, Felipe Contreras
<felipe.contreras@gmail.com> wrote:
> On Wed, Apr 3, 2013 at 6:25 PM, Max Horn <max@quendi.de> wrote:
>> On 03.04.2013, at 03:31, Felipe Contreras wrote:
>
>>> I only learned about it recently, I've looked at the history and to me
>>> it seems rather chaotic, and a lot of the code was simply copied from
>>> git-remote-hg without comment.
>>
>> gitifyhg was scrapped and completely restarted from scratch at some point. Based largely on your git-remote-hg code. A bit more on its history can be read here:
>>   http://archlinux.me/dusty/2013/01/06/gitifyhg-rewritten/

Please don't CC the gitifyhg mailing list, unlike vger mailing lists
(or any other sane list), it doesn't accept mail from non-subscribers,
which makes communication with outsiders much more difficult, as
demonstrated by this.

---
We're writing to let you know that the group you tried to contact
(gitifyhg) may not exist, or you may not have permission to post
messages to the group. A few more details on why you weren't able to
post:

 * You might have spelled or formatted the group name incorrectly.
 * The owner of the group may have removed this group.
 * You may need to join the group before receiving permission to post.
 * This group may not be open to posting.
---

-- 
Felipe Contreras

  reply	other threads:[~2013-04-04  6:47 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-02 19:02 [PATCH 00/13] remote-hg: general updates Felipe Contreras
2013-04-02 19:02 ` [PATCH 01/13] remote-hg: trivial cleanups Felipe Contreras
2013-04-02 19:02 ` [PATCH 02/13] remote-hg: add missing config variable in doc Felipe Contreras
2013-04-02 19:02 ` [PATCH 03/13] remote-hg: properly report errors on bookmark pushes Felipe Contreras
2013-04-02 19:02 ` [PATCH 04/13] remote-hg: fix for files with spaces Felipe Contreras
2013-04-02 19:02 ` [PATCH 05/13] remote-hg: make sure fake bookmarks are updated Felipe Contreras
2013-04-02 19:02 ` [PATCH 06/13] remote-hg: trivial test cleanups Felipe Contreras
2013-04-02 19:02 ` [PATCH 07/13] remote-hg: redirect buggy mercurial output Felipe Contreras
2013-04-02 19:58   ` Junio C Hamano
2013-04-02 20:22     ` Felipe Contreras
2013-04-02 20:36       ` Junio C Hamano
2013-04-04 15:07         ` Felipe Contreras
2013-04-04 16:29           ` Junio C Hamano
2013-04-02 19:02 ` [PATCH 08/13] remote-hg: split bookmark handling Felipe Contreras
2013-04-02 19:02 ` [PATCH 09/13] remote-hg: refactor export Felipe Contreras
2013-04-02 19:02 ` [PATCH 10/13] remote-hg: update remote bookmarks Felipe Contreras
2013-04-02 19:03 ` [PATCH 11/13] remote-hg: force remote push Felipe Contreras
2013-04-02 19:03 ` [PATCH 12/13] remote-hg: don't update bookmarks unnecessarily Felipe Contreras
2013-04-02 19:03 ` [PATCH 13/13] remote-hg: update tags globally Felipe Contreras
2013-04-02 19:55 ` [PATCH 00/13] remote-hg: general updates Junio C Hamano
2013-04-02 20:27   ` Felipe Contreras
2013-04-02 20:47     ` Junio C Hamano
2013-04-02 20:09 ` John Keeping
2013-04-02 22:23   ` Max Horn
2013-04-03  1:31     ` Felipe Contreras
2013-04-03  9:20       ` Felipe Contreras
2013-04-03  9:23       ` Antoine Pelisse
2013-04-05  8:26         ` Felipe Contreras
2013-04-04  0:25       ` Max Horn
2013-04-04  6:42         ` Felipe Contreras
2013-04-04  6:46           ` Felipe Contreras [this message]
2013-04-04  9:07             ` Max Horn
2013-04-04  9:35               ` Felipe Contreras
2013-04-05 22:30           ` Max Horn
2013-04-06  0:45             ` Felipe Contreras
2013-04-06 14:09               ` Philip Oakley
2013-04-06 16:01                 ` Felipe Contreras
2013-04-06  1:28             ` Junio C Hamano
2013-04-06  1:47               ` Felipe Contreras
2013-04-07  3:32                 ` Junio C Hamano
2013-04-04 18:11       ` Jed Brown
2013-04-04 18:34         ` Junio C Hamano
2013-04-04 19:23           ` Jed Brown
2013-04-04 19:45             ` Felipe Contreras
2013-04-04 18:41         ` Felipe Contreras
2013-04-04 19:01           ` Jed Brown
2013-04-04 16:14     ` Felipe Contreras
2013-04-05 11:45       ` Felipe Contreras

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=CAMP44s3HcLji22JDoSVZG_cLca8LXTbUPuVv8SbAM1yTqn8zcw@mail.gmail.com \
    --to=felipe.contreras@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=john@keeping.me.uk \
    --cc=max@quendi.de \
    --cc=peff@peff.net \
    /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.
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 NNTP newsgroup(s).