From: dtk <d.t.k@gmx.de>
To: Damien Leone <damien.leone@fensalir.fr>
Cc: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] Maildir support
Date: Mon, 11 Apr 2011 23:44:51 +0200 [thread overview]
Message-ID: <1302557683-sup-109@minibox> (raw)
In-Reply-To: <1302513523-sup-904@mailer>
Hi Damien,
Excerpts from Damien Leone's message of Mon Apr 11 11:22:09 +0200 2011:
> By default sup doesn't modify the sources at all.
why is that? I thought the way a MUA is supposed to work with a maildir is
rather straight forward[0]?
> There is a branch
> that allows backward synchronization, you will find more informations
> at the following address:
>
> http://www.mail-archive.com/sup-devel@rubyforge.org/msg00983.html
Thanks for the hint!!
I am a bit suspicious, though :| I don't know much about git, but doesn't that
essentially mean that the branch is always stuck behind the features in master
until the new features have manually been merged in?
And that for every release of master a manual release of the 'maildir' branch
has to be made?
Additionally, I consider this a very basic feature. What happens, if there is
another basic feature that is maintained in _another_ branch? How will I ever be
able to use them together?
You know, I'm just wondering why this feature isn't merged in upstream. Are
there any reasons why anyone would _not_ want proper maildir handling? Or is this
just a political decision (scared, since I've seen a few of those pull down cool
projects :/)?
Anyway, thanks for your fast reply!
dtk
----------
[0]http://en.wikipedia.org/wiki/Maildir#Technical_operation
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
next prev parent reply other threads:[~2011-04-11 21:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-11 8:08 dtk
2011-04-11 9:22 ` Damien Leone
2011-04-11 21:44 ` dtk [this message]
2011-04-12 7:34 ` Damien Leone
2011-04-12 20:41 ` dtk
2011-04-12 21:43 ` Matthieu Rakotojaona
2011-04-12 22:18 ` dtk
2011-04-11 13:05 ` Ruthard Baudach
2011-04-11 21:58 ` dtk
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=1302557683-sup-109@minibox \
--to=d.t.k@gmx.de \
--cc=damien.leone@fensalir.fr \
--cc=sup-talk@rubyforge.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox