CMD.EXE patchset 1->6

[Ann & Jason Edmeades]

Apologies if this set arrives multiple times - I sent it all on Friday, and
the mailing list only shows 1,2 and 4. I sent then again tonight separately,
and immediately 3 went missing... 

FYI I had this problem before the last hardware upgrade on winehq, and it
appeared fixed since then. I'll start copying a gmail account in future to
confirm what I am seeing, but last time some emails got delayed about a
month in transit and eventually appeared, but ONLY when winehq was involved,
gmail, hotmail, my own email addr etc all got immediate copies...

Regards,
Jason

[Robert Shearman]

Ann & Jason Edmeades wrote:
> Apologies if this set arrives multiple times - I sent it all on Friday, and
> the mailing list only shows 1,2 and 4. I sent then again tonight separately,
> and immediately 3 went missing...
>
> FYI I had this problem before the last hardware upgrade on winehq, and it
> appeared fixed since then. I'll start copying a gmail account in future to
> confirm what I am seeing, but last time some emails got delayed about a
> month in transit and eventually appeared, but ONLY when winehq was involved,
> gmail, hotmail, my own email addr etc all got immediate copies...

I believe what is happening is that the WineHQ mail server only accepts 
one SMTP connection at a time. This will probably reject half the 
messages sent by your mail server. Then they will get resent after a 
short period of time, but in batches so more messages will get rejected 
and then resent after a longer period of time, and so on until all the 
messages have been sent.

What probably sets your mail server apart from the gmail servers, for 
example, is that gmail probably sends out each message individually, 
rather than batching it with other messages bound for WineHQ.

-- 
Rob Shearman

[Ann & Jason Edmeades]

> I believe what is happening is that the WineHQ mail server only accepts 
> one SMTP connection at a time. This will probably reject half the 
> messages sent by your mail server. Then they will get resent after a 
> short period of time, but in batches so more messages will get rejected 
> and then resent after a longer period of time, and so on until all the 
> messages have been sent.
> What probably sets your mail server apart from the gmail servers, for 
> example, is that gmail probably sends out each message individually, 
> rather than batching it with other messages bound for WineHQ.

Hiya,

(Sorry - been away for 2 weeks so just catching up)

Maybe Demon are caching, I don't know if I can tell - files do turn up
eventually. I've just set up msmtp so I can send my emails in through a
gmail account instead, so I'll give that a try

Alexandre - How does the email address get into the change log, is it a
manual process or by hand. Ideally I'd like my main email address to be the
one in the Changelog, rather than the gmail one which is purely to see if it
resolves the problems I am having sending in patchsets - Is there any way I
can make this easy for you?

Regards,
Jason

[Jesse Allen]

On 5/25/07, Ann & Jason Edmeades <us(a)edmeades.me.uk> wrote:
> Hiya,
>
> (Sorry - been away for 2 weeks so just catching up)
>
> Maybe Demon are caching, I don't know if I can tell - files do turn up
> eventually. I've just set up msmtp so I can send my emails in through a
> gmail account instead, so I'll give that a try
>
> Alexandre - How does the email address get into the change log, is it a
> manual process or by hand. Ideally I'd like my main email address to be the
> one in the Changelog, rather than the gmail one which is purely to see if it
> resolves the problems I am having sending in patchsets - Is there any way I
> can make this easy for you?

With git commit, you can use the --author switch
for example:
$ git commit -a --author "Jesse Allen <email(a)somedomain.org>"
And then when you generate your patch set, it will have the address
you wanted. I do this so that I don't end up with my local machine's
address in my patches.

Jesse

[Ann & Jason Edmeades]

> > Alexandre - How does the email address get into the change log, is it a
> > manual process or by hand. Ideally I'd like my main email address to be
> > the
> > one in the Changelog, rather than the gmail one which is purely to see if
> > it
> > resolves the problems I am having sending in patchsets - Is there any way
> > I
> > can make this easy for you?
> With git commit, you can use the --author switch

Thanks - I'll have a play. I noticed git send-email asks who it should
appear from, and I have configured it to be my other account so I am waiting
to see what that does with it - Submitting it now :-)

Jason

[Detlef Riekenberg]

On Fr, 2007-05-25 at 12:35 -0700, Jesse Allen wrote:
> With git commit, you can use the --author switch
> for example:
> $ git commit -a --author "Jesse Allen <email(a)somedomain.org>"

Set "user.email" and "user.name" once with:

git repo-config 



-- 
 
By by ... Detlef

[Ann & Jason Edmeades]

> > With git commit, you can use the --author switch
> > for example:
> > $ git commit -a --author "Jesse Allen <email(a)somedomain.org>"
> > Set "user.email" and "user.name" once with:
> > git repo-config

Thanks! I found I'd already done it when installing git (must have made a
mistake and actually read the docs when doing the install!!)

Jason