Hi, On Fri, Nov 09, 2012 at 10:31:47AM +0100, Dmytro Milinevskyy wrote: > Hi Felipe, > > On Thu, Nov 8, 2012 at 8:30 PM, Felipe Balbi <balbi@xxxxxx> wrote: > > Hi, > > > > On Thu, Nov 08, 2012 at 08:07:57PM +0100, Dmytro Milinevskyy wrote: > >> > On Wed, Nov 07, 2012 at 02:14:00PM +0100, Dmytro Milinevskyy wrote: > >> >> Unfortunately I have some issues with git send-email. > >> >> I've attached the patch itself .. > >> > > >> > I'll apply it like that this time, but try to figure out how to send > >> > patches properly. We have some very helpful hints on > >> > Documentation/email-clients.txt which are hugely underused ;-) > >> > > >> well, I try to follow the rules as much as possible as long as tools > >> work ... =) > > > > git send-email has thousands of users and it works fine for them > > (including myself). Maybe you just misconfigured it ?!? ;-) > > > No, I was using it in the past w/o any issue. > In fact initial versions of the patch were sent exactly with git-send-email. > > However I lost my internet connection at home(some issues with ISP) > and at work place network environment somehow blocks > git-send-email(though thunderbird still can connect to the smtp server > ..). I don't think smtp server can make that distinction. Except for the message-id, there's nothing there which would help smtp server to figure out you're using git send-email. On top of that, it would be just extra work to maintain rules to block a tool which is essentially just sending an email. Make sure you're not missing some authentication with the mail server on your git send-email configuration. my 2 cents. -- balbi
Attachment:
signature.asc
Description: Digital signature
