The reason I put "list" in quotes was because I wasn't sure of the form. I've never followed -bugs, but I do frequently skim the archive. And I understand why others follow or skim -commits. I was okay with the interface TortoiseSVN provided me when grabbing the latest code if I wanted to further investigate changes I saw (TortoiseGit hasn't been as good, but I'll give it the benefit of the doubt for now that I'm just using it incorrectly) But it appears now I have to skim the -bugs archive and "something else" in Gerrit (because I don't really want it all emailed to me) to get the same information that used to all come through -bugs? Still trying to get a handle on that change to my "workflow". I just feel like I'm working a lot harder to do the same level of "monitoring" of Wireshark than I was in the past. So I figured I might be doing something wrong and should ask. -----Original Message----- From: Evan Huus <eapa...@gmail.com> To: Developer support list for Wireshark <wireshark-dev@wireshark.org> Sent: Wed, Feb 12, 2014 5:10 pm Subject: Re: [Wireshark-dev] -commits emails On Wed, Feb 12, 2014 at 5:03 PM, <mman...@netscape.net> wrote: > On a related note, it seems like Gerrit encourages more comments within its > interface when discussing a bug/enhancement then doing it Bugzilla (where > all outside patches used to go through). It was (is) always nice to have a > "masochist" (-bugs subscriber) interject something into a bug in Bugzilla > they weren't necessarily "following". Does Gerrit create the need for yet > another "list" to follow to get the same information? Individuals can choose to watch "all comments" for a project in their personal gerrit preferences. There shouldn't be a need for an actual mailing list. > -----Original Message----- > From: Gerald Combs <ger...@wireshark.org> > To: alexis.lagoutte <alexis.lagou...@gmail.com>; Developer support list for > Wireshark <wireshark-dev@wireshark.org> > Sent: Mon, Feb 10, 2014 2:50 pm > Subject: Re: [Wireshark-dev] -commits emails > > On 2/10/14 10:41 AM, Alexis La Goutte wrote: >> >> And as of this morning (or perhaps slightly earlier) I've stopped >> receiving them at all...? >> >> Yes, i confirm too... > > They've been mis-sent since Thursday. (It might help if the script were > running in production mode instead of test mode.) There are 21 missing > commits. I'll fix the script and resend the messages shortly. > ___________________________________________________________________________ > Sent via: Wireshark-dev mailing list <wireshark-dev@wireshark.org> > Archives: http://www.wireshark.org/lists/wireshark-dev > Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev > mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe > > > ___________________________________________________________________________ > Sent via: Wireshark-dev mailing list <wireshark-dev@wireshark.org> > Archives: http://www.wireshark.org/lists/wireshark-dev > Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev > mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe ___________________________________________________________________________ Sent via: Wireshark-dev mailing list <wireshark-dev@wireshark.org> Archives: http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
___________________________________________________________________________ Sent via: Wireshark-dev mailing list <wireshark-dev@wireshark.org> Archives: http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
