On Mon, Jun 02, 2014 at 10:20:24AM -0700, Alex Wang wrote:
> Hey Flavio,

Hi Alex,

> Quote from Ben,
> 
> """
> when VMware QA gives us a bug report, through the VMware bug tracker, we
> include the number in the change log entry, and that others are welcome to
> include their internal tracking IDs when they submit changes.
> """

I think it's a good idea to record the bug number in the changelog.
However, it would be nice to have some additional reference to whether
this is VMware bz, or a Red Hat bz, or Debian bz, or Fedora bz, so forth
and so on.

Thanks
fbl

> Thanks,
> Alex Wang,
> 
> 
> On Mon, Jun 2, 2014 at 7:32 AM, Flavio Leitner <f...@redhat.com> wrote:
> 
> > On Sun, Jun 01, 2014 at 10:04:30PM -0700, Alex Wang wrote:
> > > This commit adds logic that marks the 'struct iface's when their
> > > status need to be updated but the current status update transaction
> > > fails.  So, the main thread can re-try the update in the next run.
> > >
> > > Bug #1256577
> >
> > Where is that bz located?
> >
> > fbl
> >
> >
_______________________________________________
dev mailing list
dev@openvswitch.org
http://openvswitch.org/mailman/listinfo/dev

Reply via email to